Fix build when UNITY_USE_COMMAND_LINE_ARGS is enabled #728
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
…ARGS to prevent -Werror=missing-declarations
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.
Turning on UNITY_USE_COMMAND_LINE_ARGS includes some new functions:
IsStringInBiggerStringUnityStringArgumentMatchesThese functions don't have prototypes other than where they are defined. Because
-Werroris enabled, this results in-Werror=missing-declarationsfailing the build.Because these functions aren't used outside this file, the don't need prototypes and can just be declared static.
All the tests passed for me after this change.
Fixes #727