If a call to `vcpkg_replace_string` makes no changes i.e doesn't
effectively replace a string, A warning is logged.
This should also help identify ports that no longer need these calls to
fix things in `.pc` files etc.
* Run through the macOS update instructions one more time. I think
they're in a pretty good state now since this is the first attempt to
rerun them since we dropped Vagrant.
* Removed Parallels references for arm64.
* Removed references to removing Vagrant because it's no longer on any
of the hosts.
* Update macOS to 14.5.
* Update XCode CLT to 14.3.
* Bulk remove vcpkg_fail_port_install calls.
Interesting ones have been split out into separate reviews, where "interesting" means "anything more than just deleting the call to vcpkg_fail_port_install",
In support of https://github.com/microsoft/vcpkg/pull/21502
* Update version database.
* Revert google benchmark changes already submitted as https://github.com/microsoft/vcpkg/pull/22728
* Repair version database.
* [many ports] call vcpkg_fixup_pkgconfig()
The ports generate pc files, but don't call vcpkg_fixup_pkgconfig() so that there are absolute paths in the pc files
* Update port-version for armadillo and polyclipping.
* Update version database.
Co-authored-by: Billy Robert O'Neal III <bion@microsoft.com>
* [geogram] Switch to github mirror (alicevision/geogram)
* [geogram] Update version files
* Clean portfile and use correct version scheme
* [geogram] Update versions file