Replies: 3 comments 2 replies
-
I don't have any good suggestions for this, @strega-nil-ms, any ideas? |
Beta Was this translation helpful? Give feedback.
0 replies
-
I believe we already have these as experimental flags - |
Beta Was this translation helpful? Give feedback.
0 replies
-
Issue #16098 mentions the experimental command line flags but I'm unclear if that's something we can use in manifest mode within CMake
|
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
-
Is your feature request related to a problem? Please describe.
We are trialling vcpkg as a git submodule to replace cmake hunter. The source code lives on a Samba share, and is used by multiple build environments including Windows and Linux. We build by creating a local build directory on the target machine, and for cmake to use the source tree on the Samba share.
Right now, vcpkg appears to always write into
VCPKG_ROOT
which is problematic for our use case, not least that writing build over a network drive is very slow (SMB is fast to read unmodified files, they get oplock cached locally, but it's dog slow if anything ever gets modified).Proposed solution
https://github.com/microsoft/vcpkg/blob/master/docs/users/config-environment.md has a
VCPKG_DOWNLOADS
environment variable to override the downloads. I'd likeVCPKG_BUILDTREES
,VCPKG_INSTALLED
andVCPKG_PACKAGES
environment variables too soVCPKG_ROOT
no longer is modified over a network drive. Then I can tell vcpkg to use directories inside my local build directory, and everything goes very considerably faster. Plus, the sameVCPKG_ROOT
can then be shared between Linux and Windows.Describe alternatives you've considered
None. Single source many target architectures is a hard requirement here. If a package manager can't do that, it's a showstopper.
Beta Was this translation helpful? Give feedback.
All reactions