Add VCPKG_TARGET_IS_BSD and VCPKG_HOST_IS_BSD#47309
Conversation
|
9de10c3 to
eb1954b
Compare
Yeah for now I reverted the changes, although I left those in the scripts that wouldn't cause any port updates.
I've wanted to submit the tool PR once this one gets merged, though I've submitted one now. |
|
I can't see how those changes could cause CI failures especially on Windows/UWP, any idea what could be causing this? |
|
Your changes to the make scripts cause rebuilds which expose the current set of baseline regressions. The baseline regressions are from this week's image updates. You probably shouldn't update the legacy make scripts in |
eb1954b to
d5e8c10
Compare
|
Close and reopen to pick up #47363 |
|
Thanks and sorry for confusion over the baseline issues. |
|
@BillyONeal could you take a look at this OS X failure, because I'm pretty sure it's also not related to this PR |
Pull request was closed
d5e8c10 to
9b96cf2
Compare
|
Closed and reopened to pick up #47326 (I'm deleting all the old macOS boxes) |
In most places where there's a check for either FreeBSD or OpenBSD we probably want to be checking for BSD in general and this will make adding support for systems like NetBSD or DragonFly easier.
9b96cf2 to
51c1d25
Compare
|
The build failure is identical to most recent full build ( https://dev.azure.com/vcpkg/public/_build/results?buildId=120541&view=results ) |
In most places where there's a check for either FreeBSD or OpenBSD we probably want to be checking for BSD in general and this will make adding support for systems like NetBSD or DragonFly easier.