[Bug driver/80271] Support environment variable CLICOLOR_FORCE to enable -fdiagnostics-color

2017-12-04 Thread macetw at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80271

Tyler Mace  changed:

   What|Removed |Added

 CC||macetw at gmail dot com

--- Comment #3 from Tyler Mace  ---
This makes a ton of sense. gcc is typically used alongside other tools like
cmake, googletest, clang (maybe), and other tools are using that specific
environment variable.

Let me put it this way:
As a build engineer, I want to minimize the steps to set up this kind of
environment within an automation framework like Jenkins (and the Ansicolor
plugin), so that I can see colorized output without digging into each tool that
needs command arguments.

[Bug driver/80271] Support environment variable CLICOLOR_FORCE to enable -fdiagnostics-color

2017-12-04 Thread macetw at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80271

--- Comment #4 from Tyler Mace  ---
The argument against environment variables doesn't make sense, when the
GCC_COLORS environment variables are used right within this feature.