Kai Pastor

The vcpkg port is at 0.25.3 now.

And again the other question from the last review: Doesn't the other target need a similar fix?

> I tested the usage on Linux and Windows (including manifest mode), and it works well. You must actually run a downstream executable (or at least ask `ldd`).

For some ports, it might help to copy the source to each build dir and build in-source.

> @ras0219-msft wants a statement about the concrete use cases that we are fixing by making a change like this, such as "qtwebengine does not build without setting `--x-buildtrees-root` ever...

> This would leave the `vcpkg-tool-lessmsi` completely unused in the registry. Delist? Hm, weren't versioned tool ports prefered over the unversioned scripts? If not even intentionally interacting (`vcpkg-tool-lessmsi` dependency +...

> We do need a vcpkg_find_acquire_program because 'scripts' like vcpkg_extract_archive can't depend on ports. It is clear that a baseline of extraction tools (e.g. the tools needed to extract lessmsi)...

Additions to `vcpkg_find_acquire_program` should be reflected in `scripts/test_ports/vcpkg-find-acquire-program`.

I'm currently testing r28 ~beta2~ RC2 aka beta3 in vcpkg. Port hdf5 gave this error (x64, static library linkage, static CRT linkage): ~~~ : && /vcpkg/android-ndk-r28-beta3/toolchains/llvm/prebuilt/linux-x86_64/bin/clang --target=x86_64-none-linux-android21 --sysroot=/vcpkg/android-ndk-r28-beta3/toolchains/llvm/prebuilt/linux-x86_64/sysroot -std=c99 -g...

> Android's libdl.a does basically nothing. It exists pretty much only to appease autoconf (there are some "does this function/library exist?" checks that for some reason check only the static...