Replies: 2 comments 3 replies
-
I now realize that a thing called |
Beta Was this translation helpful? Give feedback.
0 replies
-
Not pretending to give a best practice, but I use this setup:
Some time ago I wrote a cmake script that does that: |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Reading the documentation about registries, I am not completely sure how to interpret
"default-registry"
andVCPKG_ROOT
.E.g. https://learn.microsoft.com/en-us/vcpkg/consume/git-registries
Context:
So far (without any registries) I have added some
FetchContent
cmake logic to get a specific commit from the vcpkg repository and run some bootstrapping code and run in manifest mode. This allows isolated and well defined behavior for what I can see by only usingVCPKG_ROOT
with the default registry provided implicitly.I am now adding a new registry (via
vcpkg-configuration.registries
) and am informed that I need to also specify adefault-registry
(or set it tonull
). I can obviously add themicrosoft/vcpkg
registry (again) but that means that I will have to keep thebaseline
(commit-ish) updated in two places and will have two git clones happening. Withnull
the registry fromVCPKG_ROOT
is completely ignored.I assume with registries specified through
vcpkg-configuration
the only thing that's used fromVCPKG_ROOT
i thevcpkg
executable and the complete checkout that I'm doing throughFetchContent
is a quite heavy operation only to bootstrap that.I could also have a vcpkg base installation (
VCPKG_ROOT
) initialized manually outside cmake. This would add a tiny bit of overhead for each contributor and would risk having an outdated vcpkg executable compared to what's defined indefault-registry
, I am unsure to what level this would be problematic.Is my understanding correct and are there some best practices to handle this?
Beta Was this translation helpful? Give feedback.
All reactions