• Jacky Wu's avatar
    Avoid no-match message in case STRIP_FLAG_HELP been set · d9b184bd
    Jacky Wu authored
    If the workaround in issue #43 is used along with the define of
    STRIP_FLAG_HELP to 1, there would be a wrong "No modules matched"
    message been print at end of the usage message.
    
    That's because we continue the loop if we see strip flag help value and
    never set the `found_match` flag to true even if we found a match.
    
    By moving the set statement above the continue, we can avoid this wrong
    message.
    d9b184bd
Name
Last commit
Last update
bazel Loading commit data...
cmake Loading commit data...
doc @ 8411df71
src Loading commit data...
test Loading commit data...
.gitattributes Loading commit data...
.gitignore Loading commit data...
.gitmodules Loading commit data...
.travis.yml Loading commit data...
AUTHORS.txt Loading commit data...
BUILD Loading commit data...
CMakeLists.txt Loading commit data...
COPYING.txt Loading commit data...
ChangeLog.txt Loading commit data...
INSTALL.md Loading commit data...
README.md Loading commit data...
WORKSPACE Loading commit data...
appveyor.yml Loading commit data...