meson: optionalise glib's development files for gtk_doc #372
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
In p11-kit, only installation prefix of glib is required to build gtk-doc. In some distro, those development files are splitted into separated package. Pulling those development files in will pull its development dependencies, too. Let's give our users an option to build gtk-doc without development files of glib.
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.
In p11-kit, only installation prefix of glib is required to build gtk-doc.
In some distro, those development files are splitted into separated
package. Pulling those development files in will pull its development
dependencies, too.
Let's give our users an option to build gtk-doc without development
files of glib.