You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
currently there's no easy/standardised way to use vcpkg in the CI on GitHub using GitHub Actions. you either have to use a 3rd-party action (which may or may not be actively maintained or follow best practices) or do it manually (clone the repo, run the bootstrap, etc.)
Proposed solution
you (the vcpkg team at Microsoft) centrally provide a GitHub Action which can be included which will always set up the latest release of vcpkg and register it in the path, set VCPKG_ROOT, CMAKE_TOOLCHAIN_FILE, etc.
the action could then also taking care of doing a shallow clone of the repo, caching it, etc. to reduce the load on GitHub if it's used often, if this is required.
Describe alternatives you've considered
instead of providing this as an action it could also be backed directly into the base images used by the GitHub Actions - after all, GitHub belongs to Microsoft :)
other build tools (e.g. rust) are also always installed by default, though maybe the user base of vcpkg isn't large enough yet to support this? and vcpkg might be updated more often than the base image, so having an action installing it might be better
category:vcpkg-featureThe issue is a new capability of the tool that doesn’t already exist and we haven’t committed
1 participant
Converted from issue
This discussion was converted from issue #28883 on January 12, 2023 01:06.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Is your feature request related to a problem? Please describe.
currently there's no easy/standardised way to use vcpkg in the CI on GitHub using GitHub Actions. you either have to use a 3rd-party action (which may or may not be actively maintained or follow best practices) or do it manually (clone the repo, run the bootstrap, etc.)
Proposed solution
you (the vcpkg team at Microsoft) centrally provide a GitHub Action which can be included which will always set up the latest release of
vcpkg
and register it in the path, setVCPKG_ROOT
,CMAKE_TOOLCHAIN_FILE
, etc.the action could then also taking care of doing a shallow clone of the repo, caching it, etc. to reduce the load on GitHub if it's used often, if this is required.
Describe alternatives you've considered
instead of providing this as an action it could also be backed directly into the base images used by the GitHub Actions - after all, GitHub belongs to Microsoft :)
other build tools (e.g. rust) are also always installed by default, though maybe the user base of
vcpkg
isn't large enough yet to support this? andvcpkg
might be updated more often than the base image, so having an action installing it might be betterAdditional context
vcpkg
related actionsBeta Was this translation helpful? Give feedback.
All reactions