Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Tag in vcpkgCommitId

See original GitHub issue

If I understand correctly, then vcpkgCommitId cannot contain a tag. But if you specify it, then I will get silently non-working cache. Workflow output with tag in vcpkgCommitId (the cache is unpacked but not used).

Issue Analytics

State:
Created 3 years ago
Comments:9 (4 by maintainers)

Top GitHub Comments

1reaction

justusranviercommented, Sep 19, 2022

the best practice is to use vcpkg as a submodule

I guess you’ve never run into this issue before, but using vcpkg as a submodule is actually a terrible idea if you need to run vcpkg on windows images because of the MAX_PATH issue.

There are several packages in vcpkg whose build process runs right up to the limit and only work if you use C:\VCPKG. Any base path longer than that and you’ll get hard to diagnose failures and confusing error messages that take a long time to track back to their root cause.

1reaction

Shaturcommented, Oct 14, 2020

Instead of specifying a tag, or a commit id, the best practice is to use vcpkg as a submodule, so that the vcpkg used is exactly the same locally and on CI.

Yes, I know, but I only need vcpkg on Windows, because on Linux I need to build a package with the versions of the libraries that are in the official repository. I would even okay with #35 or #44 to have latest possible versions of the libraries.