Respect VERBOSE environment variable if already set before in verbose mode #506
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.
At the moment it is not possible to build a workspace with catkin_tools in verbose mode without also switching
make
to verbose mode.For our continuous integration jobs I would like to have a way to see the normal output of cmake and make (with
catkin build -v
), but without all the clutter produced bymake
if theVERBOSE
environment variable is set. The alternative is-i
, but it does not behave well if the output is not a terminal and if multiple packages are built in parallel.Note that setting
VERBOSE=0
does not have the desired effect. The variable needs to be defined, but empty to disable make's verbosity (VERBOSE= catkin build -v ...
).Maybe the whole section was a leftover from debugging catkin_tools? The GitHub issue template explicitly asks to set VERBOSE=1 although
-v
already implies that in the current version: