Replies: 1 comment 1 reply
-
and the 5th time I ran this, it pulled all of them. I guess its transient, but if this does happen again, how do I use --debug when in manifest mode running from cmake? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have binary caching working well locally. I upload to an artifactory server, and I run from a docker container, so everything is always the same. Locally it is always finding the binaries. My issue is on the build system, which is Github actions. Even though I am running the same container, it is only saying 113 of the 140 some libraries are a match and is rebuilding them. I am using
set(VCPKG_DEFAULT_HOST_TRIPLET x64-linux-dynamic)
set(VCPKG_TARGET_TRIPLET x64-linux-dynamic)
and I am in manifest mode through cmake. I'm not even sure how to go about debugging this on the build system. Or if it even matters since vcpkg has decided the docker image is different when run from there. Is this dependent on processor?
Beta Was this translation helpful? Give feedback.
All reactions