mirror of https://github.com/microsoft/vcpkg.git
47633daa65
Avoid wrong use of popular but ambiguous variables (`WIN32` etc.) in scripts and portfiles by detection in CI. Sometimes the variables are used wrongly, and sometimes this isn't caught in PR review. This PR tries to catch those variables (when in the active code path in script mode). [This can happen to every contributor](https://github.com/microsoft/vcpkg/pull/34356#discussion_r1360074122), even if he/she knows the rules ... vcpkg is raising the bar higher than usual, having to deal with targets and hosts even in script mode. (`b2-options.cmake` (boost fragment) shows where we get if we don't pay attention: the same code being used in script mode (`WIN32` meaning host) and in project mode (`WIN32` meaning target).) The new check doesn't break any user builds because it relies on command line options. However it changes the ABI hashes. |
||
|---|---|---|
| .. | ||
| angle | ||
| azure-pipelines | ||
| boost | ||
| buildsystems | ||
| cmake | ||
| detect_compiler | ||
| get_cmake_vars | ||
| ifw | ||
| posh-vcpkg/0.0.1 | ||
| templates | ||
| test_ports | ||
| toolchains | ||
| addPoshVcpkgToPowershellProfile.ps1 | ||
| bootstrap.ps1 | ||
| bootstrap.sh | ||
| build_info.cmake | ||
| ci.baseline.txt | ||
| file_script.py | ||
| generateBaseline.py | ||
| generatePortVersionsDb.py | ||
| ports.cmake | ||
| tls12-download-arm64.exe | ||
| tls12-download.exe | ||
| update-vcpkg-tool-metadata.ps1 | ||
| vcpkg-tool-metadata.txt | ||
| vcpkgTools.xml | ||
| vcpkg_completion.bash | ||
| vcpkg_completion.fish | ||
| vcpkg_completion.zsh | ||