[PATCH] Allow using ANSI escape sequences on Windows

Reid Kleckner rnk at google.com
Tue Sep 3 11:21:10 PDT 2013


On Mon, Sep 2, 2013 at 12:10 PM, Nico Rieck <nico.rieck at gmail.com> wrote:

> On 02.09.2013 20:45, Chandler Carruth wrote:
>
>> On nix-ish platforms, -fcolor-diagnostics actually enables colors even for
>> pipes, and so works with Ninja or other build systems that use pipes. Is
>> the problem that you need to switch from console APIs to produce the
>> colors
>> to ANSI escapes?
>>
>
> Exactly.
>
>
>  How about a -fansi-escape-colors or some such?
>>
>> Generally, I'd like to avoid the use of the environment variables. Command
>> line switches and such are easier to test, set, and audit in most cases.
>>
>
> I initially opted to use an environment variable to keep the impact small.
> But if you think a command line switch would be better, that's fine with me
> and I'll rewrite this.


There is always the little-known QA_OVERRIDE_GCC3_OPTIONS if you want to
flip color diagnostics on or off without re-running CMake.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20130903/55425190/attachment.html>


More information about the llvm-commits mailing list