This repository has been archived by the owner on Mar 9, 2021. It is now read-only.
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.
Vanilla iOS projects define
DEBUG
to be 1 in the Debug build configuration, and don't defineDEBUG
at all in the Release build configuration. That means that if you make a release buildDEBUG
is implicitly 0, but if you turn on the -Wundef warning flag you'll get warnings about this implicit value.This pull request explicitly makes sure both that
DEBUG
is defined and that its value evaluates to true. It also fixes another warning related to using an iOS-only macro in the Mac project.This mirrors a change I made to our
FLAnimatedImage
project at Flipboard/FLAnimatedImage#66.