build: add feature to generate pkg-config metadata file at build time #128
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
This is a bit of a hack, but cargo doesn't exactly make this easy.
This can be used to build exernal projects that use libquiche.{a,so}
(e.g. curl) without having to hard-code paths.
To enable it, pass "--features pkg-config-meta" to cargo build.
bagder
pushed a commit
to curl/curl
that referenced
this pull request
Aug 20, 2019
This removes the need to hard-code the quiche target path in configure.ac. This depends on cloudflare/quiche#128 Closes #4237
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.
This is a bit of a hack, but cargo doesn't exactly make this easy.
This can be used to build exernal projects that use libquiche.{a,so}
(e.g. curl) without having to hard-code paths.
To enable it, pass "--features pkg-config-meta" to cargo build.