Use Travis CI to check for compilation warnings #48
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 PR allows Travis CI to compile and perform specific checks on the consistency of code, and ideally guard against introducing "bad code". This is done by passing FFLAGS to pymake, specifically
-Werror
which treats all warnings as errors, and fails the Travis CI with a log of compilation steps and errors, which is handy to see.So far, I've added a few specific warnings flags from previous commits for tabs. And added to this PR is
-Wcharacter-truncation
, as there was a minor discrepancy between the data types.When potential issues are resolved in the code for each warning type (docs here), then that flag can be added to
fflags
inautotest/config.py
for testing on Travis CI.