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.
* [magnum/-plugins] Remove obsolete patches that no longer apply
Signed-off-by: Squareys <squareys@googlemail.com>
* [corrade] Make feature to flag translation consistent to fix warning
Consistent with magnum & magnum-plugins
Signed-off-by: Squareys <squareys@googlemail.com>
* Fix warning message for dlls without matching pdbs always displayed
Signed-off-by: Squareys <squareys@googlemail.com>
* Fix the baseline version
* Revert the changes in vcpkg_copy_pdbs.cmake
Co-authored-by: PhoebeHui <20694052+PhoebeHui@users.noreply.github.com>
* [magnum,magnum-plugins] Add vulkan and shaderconverter features
Signed-off-by: Squareys <squareys@googlemail.com>
* [magnum,-plugins] Add warning for features unavailable in non-head version
Signed-off-by: Squareys <squareys@googlemail.com>
* update version record
Co-authored-by: JackBoosY <yuzaiyang@beyondsoft.com>
