Replies: 1 comment 2 replies
-
Sure. If I understand you correctly, you are looking for something in between. Since the effort is significantly higher - what additional value would this bring to your team? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I keep vcpkg as a submodule in my project, located in
external/vcpkg/
(it is the only submodule in my project)I needed to update a version of one of my dependencies, requiring I move-up the baseline and thus update the version of vcpkg. In my root CMakeLists.txt, I have the following:
This appears to work fine and fetches the submodule when the project is first cloned, and then uses the vcpkg manifest to fetch all dependencies. Great! The trouble starts when I ever try to update the vcpkg version, this has been an issue in the past as well, but its now getting to be very frustrating as more people are working on the projection.
My first attempt was to update it using this:
Re-running CMake and it couldn't find a single one of my dependencies saying that none of the versions existed. I reset everything, then tried:
This appeared to work but then it just hanged on:
So I finally just completely deleted the directory
external/vcpkg
and NOW everything seemed to work correctly. But that means anyone working with this project is also going to have to manually go deleteexternal/vcpkg
when they pull any of these changes. Is there a better way to handle this? I am working on just ditching including vcpkg as a submodule and requiring users to have their own copy, but it would be nice to have an optional submodule copy or something (if the user just wants to quickly build the application, set a-DUSE_VCPKG_SUBMODULE
or something like that). This seems overly annoying, though I'm also not familiar with submodules so that might just be a problem with how submodules workBeta Was this translation helpful? Give feedback.
All reactions