Manifest Export on Internal Network #47307
mccartnm
started this conversation in
Show and tell
Replies: 1 comment
-
|
When in doubt! Cheat! Okay - so I've gone off the tracks a bit and explored the So I copied the Solution(ish)So to recap:
This is all a bit cheeky but desperate times and all |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello vcpkg community!
After building an
vcpkg exportof various libraries required and bringing them into a network without internet access I've run into some roadblocks trying to use these materials.From the vcpkg export documentation it states:
But we seem to be hitting multiple issues with this impromptu-SDK. We were seeing the issue missing triplets (because the
tripletsdirectory was not available).I manually added the
triplets/x64-windows.cmakeunder the example export and then it started complaining aboutvcpkg-tools.jsonand so on. Suffice it to say I'm not sure these standalone bundles are quite standalone with my current workflow and I'm hoping I've just missed a step along the way!Question:
Is it assumed, that even with an exported manifest, that the target machine still requires a local bootstrapped version of vcpkg and, if so, how would one obtain that on a network without net access? Should we zip up a bootstrapped VCPKG_ROOT from another machine? Even if we do that, does vcpkg still require internet at random points along that process and it's still not possible?
Beta Was this translation helpful? Give feedback.
All reactions