Add support for llvm-objdump to applocal.ps1

[Chronial]

This fixes #11467 and together with #11466 seems to be everything needed to have clang support under windows for x64 builds.

[MVoz]

tested file.exe
https://github.com/julian-r/file-windows/releases

https://github.com/brechtsanders/pedeps/releases

portable across different platforms (Windows, macOS, *nix)
no dependencies

small one file listpedeps

listpedeps.exe "file.exe" | ? { $_ -match "[^ ].dll" }

libmagic.dll
VCRUNTIME140.dll
api-ms-win-crt-heap-l1-1-0.dll
api-ms-win-crt-runtime-l1-1-0.dll
api-ms-win-crt-convert-l1-1-0.dll
api-ms-win-crt-environment-l1-1-0.dll
api-ms-win-crt-string-l1-1-0.dll
api-ms-win-crt-stdio-l1-1-0.dll
api-ms-win-crt-locale-l1-1-0.dll
api-ms-win-crt-math-l1-1-0.dll
KERNEL32.dll

llvm-objdump -p "file.exe" | ? { $_ -match "^ {4}DLL Name: .*\.dll" } | % { $_ -replace "^ {4}DLL Name: ","" }

libmagic.dll
VCRUNTIME140.dll
api-ms-win-crt-heap-l1-1-0.dll
api-ms-win-crt-runtime-l1-1-0.dll
api-ms-win-crt-convert-l1-1-0.dll
api-ms-win-crt-environment-l1-1-0.dll
api-ms-win-crt-string-l1-1-0.dll
api-ms-win-crt-stdio-l1-1-0.dll
api-ms-win-crt-locale-l1-1-0.dll
api-ms-win-crt-math-l1-1-0.dll
KERNEL32.dll

dumpbin /DEPENDENTS "file.exe" | ? { $_ -match "^ [^ ].*\.dll" } | % { $_ -replace "^ ","" }

libmagic.dll
VCRUNTIME140.dll
api-ms-win-crt-heap-l1-1-0.dll
api-ms-win-crt-runtime-l1-1-0.dll
api-ms-win-crt-convert-l1-1-0.dll
api-ms-win-crt-environment-l1-1-0.dll
api-ms-win-crt-string-l1-1-0.dll
api-ms-win-crt-stdio-l1-1-0.dll
api-ms-win-crt-locale-l1-1-0.dll
api-ms-win-crt-math-l1-1-0.dll
KERNEL32.dll

[PhoebeHui]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ras0219-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ras0219-msft]

This LGTM in principle, but will require testing.

[Chronial]

@ras0219-msft Is there anything I can do here? This obviously needs x64 windows clang, so testing this on the current CI is not feasible?

[Milerius]

very interesting pr for people like me that use clang on windows

[BillyONeal]

Do you think you could add a test of this to the end-to-end-tests.ps1? (Not required to merge it, but it would be nice)

[BillyONeal]

This obviously needs x64 windows clang

We currently install whichever version Visual Studio installs, which I think is an x86 version; is that acceptable?

vcpkg/scripts/azure-pipelines/windows/provision-image.txt

Lines 119 to 120 in 5a97bb2

	'Microsoft.VisualStudio.Component.VC.Llvm.ClangToolset',
	'Microsoft.VisualStudio.Component.VC.Llvm.Clang'

[Chronial]

@BillyONeal Thanks for taking time for this issue. I will try to have a look at end-to-end-tests on Monday.

We currently install whichever version Visual Studio installs, which I think is an x86 version; is that acceptable?

I see no reason why x86 wouldn't be fine. I honestly can't quite remember why I wrote x64 back then – probably just because that's the architecture we are using. But it's very good to know that there is a clang available on the CI machines.

[strega-nil]

I'm merging, since we have people who are waiting on this. @Chronial, could you look at the e2e tests and open a new PR?

[Chronial]

@strega-nil thanks for merging. It got a bit busy this week – I'll see to the test when I find time.