Kai Pastor

> I just noticed that vcpkg also supports `MINGW`? That's why I use it... --- The CMake config must also use a cache variable, so that users can change it...

> > The CMake config must also use a cache variable, so that users can change it at time of use. I realize now that external input is respected in...

For review: [Report on colors and symbols](https://github.com/user-attachments/files/15896087/index.html.zip) 

Somewhat related to #45812.

Okay. Thanks for reporting nevertheless.

@jasjuang https://github.com/microsoft/vcpkg/discussions/45327 should be discussed there, not in this PR.

x64-windows: ~~~ -- Performing post-build validation D:\a\_work\1\s\ports\lunarg-vulkantools\portfile.cmake: warning: The following executables were found in ${CURRENT_PACKAGES_DIR}/bin or ${CURRENT_PACKAGES_DIR}/debug/bin. Executables are not valid distribution targets. If these executables are build tools, consider...

I can't help you with duplicating the full enviroment. vcpkg CI is my only MSVC environment, with the logs it produces. - This can't be useful for the port: https://github.com/LunarG/VulkanTools/blob/e088d553426a3036270701d07dde28bf33d318be/vkconfig_gui/CMakeLists.txt#L54-L55...

This will need many changes. - No `vcpkg_from_git` - Use vcpkg ports as dependencies. - Let vcpkg control the flags. Does it really have to use nmake? This limits the...

> I tried to fix vcpkg.json for LLVM but it did not work, it just fallback to default features of LLVM package. In a port manifest, `default-features` is just an...