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.
* first batch of xwindow PR ports - up to dbus
* first batch of xwindow PR ports - up to dbus
* format manifest
* version stuff
* remove if block
* version stuff
* fix xcb hash
* fix xproto dependency on meson blocking cross builds
* adjust message
* use X11_xcb_LIB
* version stuff
* put xlib arm64-windows on baseline
* fix dbus on osx and linux
* version stuff
* forget to set the value
* fix --export-dynamic on osx
* version dbus
* ci-retrigger
* add license (needs tool update)
* version adjustments
* version update
* remove unnecessary comments
* v db
* Apply suggestions from code review
Co-authored-by: Billy O'Neal <bion@microsoft.com>
* nitpicks
* rename xau to libxau
* use vcpkg_install_copyright and silence usage
* xtrans silence usage
* format-manifest
* v db
* make license null for ports without exact match
* xdmcp rename to libxdmcp
* merge x11 wrapper into xlib
rename xlib to libx11 to avoid a metaport
* v db
* missed dbus depending on x11.
* v db
* Update scripts/ci.baseline.txt
Co-authored-by: LilyWangLL <94091114+LilyWangLL@users.noreply.github.com>
Co-authored-by: Alexander Neumann <you@example.com>
Co-authored-by: JackBoosY <yuzaiyang@beyondsoft.com>
Co-authored-by: Billy O'Neal <bion@microsoft.com>
