-
Notifications
You must be signed in to change notification settings - Fork 276
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
Configuring overlay ports and overlay triplets through the manifest #743
Conversation
@microsoft-github-policy-service agree [company="microsoft"] |
@microsoft-github-policy-service agree company="microsoft" |
Currently relative paths are relative to the CWD and not to the manifest root. And I guess e2e test will come to test relative paths in manifest file and manifest root != CWD. I really like this change 👍 |
The only issue I have with adding this stuff into the manifest is that the manifest becomes kind of a configuration file for vcpkg instead of a clean dependency definition. Maybe vcpkg should add a new differentiation and add a |
That is, |
Wait, that's what this PR already does. @Neumann-A I think the "vcpkg.json is the durable/transitive declaration of dependencies" is unaffected here. |
Maybe the title of the PR should be changed? Or is |
We consider
Yes, and just like registries you could also configure overlays in |
bc6a941
to
8c674e0
Compare
Is this documented somewhere? I always thought you need to have two different files (vcpkg.json; vcpkg-configuration.json). |
That would be my fault, I don't think it is documented other than the comment I made on the PR #239. |
I added this to the docs PR I have open (currently on the description of this PR) |
a48a9e0
to
8294341
Compare
Thanks! |
Docs PR: microsoft/vcpkg#27172