-
Notifications
You must be signed in to change notification settings - Fork 6.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[vcpkg baseline][vcpkg-build-make] Use the same MSYS_ROOT in configure and build #19325
[vcpkg baseline][vcpkg-build-make] Use the same MSYS_ROOT in configure and build #19325
Conversation
cc @Neumann-A |
I guess this PR will break Every call to |
@dg0yt That's not related to the configure step but related to the build step. |
Indeed. And it works, due to the default packages. Still, this proliferates different interfaces for defining the msys environment.
This creates two different msys roots for a single package like starlink-ast (and a third one if acquiring pkg-config). I don't think this is the best way forward. |
@Neumann-A what do you think about? |
Yes, the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!
After committing all other changes, the version database must be updated
git add -u && git commit
git checkout a863c84812089836a3c0f2f215ab3e2579fc8acf -- versions
./vcpkg x-add-version --all
Diff
diff --git a/versions/baseline.json b/versions/baseline.json
index 8cadbc5..eb0a367 100644
--- a/versions/baseline.json
+++ b/versions/baseline.json
@@ -6086,7 +6086,7 @@
},
"starlink-ast": {
"baseline": "9.2.4",
- "port-version": 0
+ "port-version": 1
},
"status-code": {
"baseline": "1.0.0-ab3cd821",
diff --git a/versions/s-/starlink-ast.json b/versions/s-/starlink-ast.json
index f357f55..a724950 100644
--- a/versions/s-/starlink-ast.json
+++ b/versions/s-/starlink-ast.json
@@ -1,5 +1,10 @@
{
"versions": [
+ {
+ "git-tree": "2fecd468269d73b6e8f29a297c4f7db771ea37c4",
+ "version-semver": "9.2.4",
+ "port-version": 1
+ },
{
"git-tree": "50f0b71ca66bd9e4ce6cb5a153e25878dd7a0600",
"version-semver": "9.2.4",
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!
After committing all other changes, the version database must be updated
git add -u && git commit
git checkout a863c84812089836a3c0f2f215ab3e2579fc8acf -- versions
./vcpkg x-add-version --all
Diff
diff --git a/versions/baseline.json b/versions/baseline.json
index 8cadbc5..eb0a367 100644
--- a/versions/baseline.json
+++ b/versions/baseline.json
@@ -6086,7 +6086,7 @@
},
"starlink-ast": {
"baseline": "9.2.4",
- "port-version": 0
+ "port-version": 1
},
"status-code": {
"baseline": "1.0.0-ab3cd821",
diff --git a/versions/s-/starlink-ast.json b/versions/s-/starlink-ast.json
index f357f55..a724950 100644
--- a/versions/s-/starlink-ast.json
+++ b/versions/s-/starlink-ast.json
@@ -1,5 +1,10 @@
{
"versions": [
+ {
+ "git-tree": "2fecd468269d73b6e8f29a297c4f7db771ea37c4",
+ "version-semver": "9.2.4",
+ "port-version": 1
+ },
{
"git-tree": "50f0b71ca66bd9e4ce6cb5a153e25878dd7a0600",
"version-semver": "9.2.4",
@@ -305,7 +309,7 @@ function(vcpkg_configure_make) | |||
# Pre-processing windows configure requirements | |||
if (VCPKG_TARGET_IS_WINDOWS) | |||
if(CMAKE_HOST_WIN32) | |||
list(APPEND MSYS_REQUIRE_PACKAGES binutils libtool autoconf automake-wrapper automake1.16 m4) | |||
list(APPEND MSYS_REQUIRE_PACKAGES binutils libtool autoconf automake-wrapper automake1.16 m4 make) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
make is in the default packages:
vcpkg/scripts/cmake/vcpkg_acquire_msys.cmake
Lines 152 to 154 in bd5ea16
if(NOT arg_NO_DEFAULT_PACKAGES) | |
list(APPEND Z_VCPKG_MSYS_PACKAGES bash coreutils sed grep gawk diffutils make pkg-config) | |
endif() |
@@ -866,4 +870,7 @@ function(vcpkg_configure_make) | |||
|
|||
SET(_VCPKG_PROJECT_SOURCE_PATH ${_csc_SOURCE_PATH} PARENT_SCOPE) | |||
set(_VCPKG_PROJECT_SUBPATH ${_csc_PROJECT_SUBPATH} PARENT_SCOPE) | |||
if (MSYS_ROOT) | |||
set(MSYS_ROOT ${MSYS_ROOT} PARENT_SCOPE) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This adds the side effect of changing MSYS_ROOT
in the parent scope without user control. I don't think this is desirable. Either the scripts interact via Z_
-prefixed variables (it is an implementation detail), or the variable name must be taken from yet another parameter.
I implemented passing of the make tool (from MSYS_ROOT or system) from |
Close this PR in a favor of #19361. |
vcpkg_acquire_msys(MSYS_ROOT)
invcpkg_build_make
will cause the extra msys components missing when building ports.For example, building
starlink-ast:x64-uwp
:In starlink-ast's portfile.cmake:
This will overwrite the value
MSYS_ROOT
and use the incorrect make.exe to build it.This code was introduced in PR #10402.