std.Build: propagate added (system) library paths from dependencies #23936
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
System libraries are already propagated; it makes sense to additionally propagate the directories in which they are specified to be found.
|
Do we also need to do this for include paths, or is that done already? |
I believe this is already done for installed/exposed include paths and headers (installHeader & installHeadersDirectory) when calling linkLibrary. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
System libraries are already propagated in the same manner; it makes sense to additionally propagate the directories in which they are specified to be found (addLibraryPath).
Fair warning, I'm not all that familiar with the intricacies of linking, so I can't be sure if this small change has some implications I haven't considered yet.