[authorization] Clarify pkgconfig requirements. Fixes JB#59315 #5
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
Thaodan
reviewed
Nov 13, 2022
vigejolla
reviewed
Nov 14, 2022
The documentation relating to pkgconfig requirements explained what needed to be added to the .pro file, but not to either the .yaml or .spec files, in order for buiding against the libraries to work. These changes make the requirements more explicit.
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.
The documentation relating to pkgconfig requirements explained what needed to be added to the .pro file, but not to either the .yaml or .spec files, in order for buiding against the libraries to work.
These changes make the requirements more explicit.