-
Notifications
You must be signed in to change notification settings - Fork 296
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[tool cache] Add option to require exact versions for abi relevant tools #234
Conversation
If a developer in a team has a different version of a abi relevant tool, the developer has to rebuild every package because the developer only gets cache misses in the binary cache. Add an option to force vcpkg to use the same version of a abi relevant tool so that you don't get binary cache misses because of different abi relevant tools.
I think this is a better alternative to the "always download" other PR. |
The question is rather if the default should be |
What do you mean by this? |
This PR seems like the best option until we're able to come up with a Grand Unified Control over external tool versions. Thanks! |
While this does now make it practical to use binary caching relying on a server to run builds, I still think it is not a great experience for users. Currently, users need to figure out why binary caching is missing then find out about two different options to disable behavior that is preventing cache hits, both compiler tracking and this new option. I propose to merge this new option and the compiler tracking option into one. I also propose making the default no compiler tracking and exact matches for CMake & PowerShell so users don't need to struggle with figuring out why binary caching isn't working. |
I also do not understand this suggestion because the ABI info includes different hashes for different packages depending on what the package's dependencies are. |
Cool! Any documentation on how to use this correctly? |
from zlib:
I want switches to disable all entries one by one and also I want to be able to add my own stuff to the abi. In general this is always a list/vector of |
@Osyotr Just pass |
Will there be a new release soon so this can be used? |
Yes, we plan to cut a release soon (though there is the US holiday Thanksgiving next week which may delay things) |
|
If a developer in a team has a different version of a abi relevant tool, the developer has
to rebuild every package because the developer only gets cache misses in the binary cache.
Add an option to force vcpkg to use the same version of a abi relevant tool so that you don't
get binary cache misses because of different abi relevant tools.