Add static flag to libheif.pc #1415
Merged
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
|
Shouldn't this only be set if it is a static build? |
|
Precisely. Hence the "Cflags.private". |
Yes, that |
How so? It's analogous to |
|
Yes, just as confusing as those.... |
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 just one (small) step in addressing e.g. #513 and #902 for clients of the static library (for which the correct OOTB build of on Windows still needs to be handled).
This is not gated by WIN32 anywhere (i.e. placeholder to be conditionally substituted by CMake), but it doesn't affect other platforms, so might as well hard code it...