v/pkgconfig: add pkgconfig path for FreeBSD base packages #21151
Conversation
This file contains 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
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.
For 3rd party software that is part of the base FreeBSD install, their pkg-config files are in /usr/libdata/pkgconfig.
This path was not in the set of default pkgconfig paths. As a result, if a module relied upon some library or include file from the base system, even as an indirect dependency, it would not be found.
I added the base path after the path for pkgconfig files that are from installing packages or ports so that packages or ports would be found preferentially over ones in the base system. For example, if a newer version of openssl was installed via the pkg command or as a port, it would be found instead of the one from the base install.