-
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] Allow CI to pass in all relevant directories and remove use of symbolic links #11483
Conversation
687bcd4
to
206c8cf
Compare
b996a00
to
544a0e5
Compare
merge? |
@@ -109,7 +109,7 @@ function(vcpkg_build_msbuild) | |||
list( | |||
APPEND _csc_OPTIONS | |||
/p:ForceImportBeforeCppTargets=${SCRIPTS}/buildsystems/msbuild/vcpkg.targets | |||
"/p:VcpkgTriplet=${TARGET_TRIPLET}" | |||
"/p:VcpkgRoot=${CURRENT_INSTALLED_DIR}/${VCPKG_TARGET_TRIPLET}" |
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.
That is wrong.
You probably want
"/p:VcpkgTriplet=${TARGET_TRIPLET}"
"/p:VcpkgRoot=${CURRENT_INSTALLED_DIR}"
nevermind just checked the targets VcpkgRoot is named wrongly
still wrong
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.
VcpkgRoot
should be renamed to VcpkgInstalledTripletRoot
instead.... (naming is hard) (or VcpkgTripletInstalledDir
)
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.
I agree :)
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.
Is ${CURRENT_INSTALLED_DIR}
installed/triplet
or just installed
?
Azure Pipelines successfully started running 1 pipeline(s). |
@@ -110,6 +110,7 @@ function(vcpkg_build_msbuild) | |||
APPEND _csc_OPTIONS | |||
/p:ForceImportBeforeCppTargets=${SCRIPTS}/buildsystems/msbuild/vcpkg.targets | |||
"/p:VcpkgTriplet=${TARGET_TRIPLET}" | |||
"/p:VcpkgRoot=${CURRENT_INSTALLED_DIR}" |
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.
is VcpkgRoot
the equivalent of CURRENT_INSTALLED_DIR
? I would expect this variable to be something like where the vcpkg
executable lives.
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.
Yes, it is like CURRENT_INSTALLED_DIR
-- the name is bad because I didn't write the script consuming the variable (it's $/scripts/buildsystems/msbuild/vcpkg.targets
). I don't want to edit that here because I don't know exactly how it interacts with vcpkg integrate install
. Would filing an issue about it and addressing in a subsequent PR be OK? (I don't want to grow this PR even bigger :) )
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.
Hmmm I guess I could make a dependent change which changes that name, stand by...
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.
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.
so should we merge 11653 first?
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.
Yes, done.
# Conflicts: # toolsrc/include/vcpkg/vcpkgcmdarguments.h # toolsrc/src/vcpkg.cpp # toolsrc/src/vcpkgcmdarguments.cpp
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.
Please update qt5-base
, shiva-sfml
, spirv-tools
version info. See documentation.
Done, thanks! |
…edDir. I could have ensured we always passed the trailing slash, but defending against it here makes it easier for users if they want to use /p themselves.
allow us to override a console provided property here. --> | ||
<VcpkgRootSanitized>$(VcpkgRoot)</VcpkgRootSanitized> | ||
<VcpkgRootSanitized Condition="!$(VcpkgRootSanitized.EndsWith('\'))">$(VcpkgRootSanitized)\</VcpkgRootSanitized> | ||
<VcpkgCurrentInstalledDirSanitized>$(VcpkgCurrentInstalledDir)</VcpkgCurrentInstalledDirSanitized> |
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.
Looks like there is a problem here.
The VcpkgCurrentInstalledDir
initialization was removed few lines above and it's empty now.
Adds
--x-foo-root=
parameters for the directories to which we have applied symlinks in the past, such as installed, buildtrees, packages, etc.This is intended to unblock #11365 which broke due the symlink workaround we previously used to get the work tree onto the VM temp disk not working with the current Scale Set Agents installation script.
Drive-by fixes: