Add to gcc compiler arg to display colors in gcc output, to generated build tasks. #8165
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
Colengms
changed the title
sean-mcmanus
approved these changes
Sep 16, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Uses
-fdiagnostics-color=always, which causes gcc colors to be used in VS Code's terminal. The default is 'auto', but gcc is unable to detect that colorization is supported by the VS Code terminal.Looking at code from gcc here: https://code.woboq.org/gcc/gcc/diagnostic-color.c.html
... It looks like colors are likely not determined to be supported in the VS Code terminal due to
GetConsoleMode()failing on Windows, andisatty()failing on Linux/Mac.