Fix the order of flags when including libpng. #94
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 apparently does matter.
bentley
reviewed
Oct 12, 2016
| @@ -1,7 +1,8 @@ | |||
| PKG_CONFIG = pkg-config | |||
| WARNFLAGS = -Wall -Werror=implicit | |||
| PNGFLAGS != ${PKG_CONFIG} --cflags libpng | |||
| REALCFLAGS = ${CFLAGS} ${WARNFLAGS} ${PNGFLAGS} -Iinclude -g \ | |||
There was a problem hiding this comment.
Broke the build. PNGFLAGS is needed for *.o, not the final executable.
|
95cd960 switches the order around without fiddling with PNG flags. Does it work? |
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.
redo of #90's 90eea80
If libpng is included first, gcc will ignore it, because it hasn't been referenced yet.