Build task isn't colored in terminal

[serfreeman1337]

Brief Issue Summary

I'm trying to get color output in terminal. Suggested workaround here #478 (comment) isn't working as expected.

Compiler errors are only colored with set(CMAKE_CXX_FLAGS -fdiagnostics-color=always) is in CMakeList.txt,
but "Building CXX Object" messages are still in white.

Switching task to shell command shows desired colored output ("Building CXX Object" messages are in green color):

{
	"version": "2.0.0",
	"tasks": [
		{
			"type": "shell",
			"label": "CMake: build and run",
			"command": "cmake --build ${workspaceFolder}/build --config Debug --target ${workspaceFolderBasename} && ${workspaceFolder}/build/${workspaceFolderBasename}",
			"group": "build"
		}
	]
}

CMake Tools Diagnostics

CMake: Log Diagnostics

{
  "os": "linux",
  "vscodeVersion": "1.72.0",
  "cmtVersion": "1.12.27",
  "configurations": [
    {
      "folder": "/home/serfreeman1337/Dev/tmp-esp32-cv-test",
      "cmakeVersion": "3.24.2",
      "configured": true,
      "generator": "Unix Makefiles",
      "usesPresets": false,
      "compilers": {
        "C": "/usr/bin/gcc",
        "CXX": "/usr/bin/g++"
      }
    }
  ],
  "cpptoolsIntegration": {
    "isReady": true,
    "hasCodeModel": true,
    "activeBuildType": "Debug",
    "buildTypesSeen": [
      "Debug"
    ],
    "requests": [
      "file:///home/serfreeman1337/Dev/tmp-esp32-cv-test/oh.cc",
      "file:///home/serfreeman1337/Dev/tmp-esp32-cv-test/tmp-esp32-cv-test.cc"
    ],
    "responses": [
      {
        "uri": "file:///home/serfreeman1337/Dev/tmp-esp32-cv-test/oh.cc",
        "configuration": {
          "includePath": [
            "/usr/include/opencv4"
          ],
          "defines": [],
          "compilerPath": "/usr/bin/g++",
          "compilerArgs": [],
          "compilerFragments": [
            "-g",
            "-std=gnu++17"
          ]
        }
      },
      {
        "uri": "file:///home/serfreeman1337/Dev/tmp-esp32-cv-test/tmp-esp32-cv-test.cc",
        "configuration": {
          "includePath": [
            "/usr/include/opencv4"
          ],
          "defines": [],
          "compilerPath": "/usr/bin/g++",
          "compilerArgs": [],
          "compilerFragments": [
            "-g",
            "-std=gnu++17"
          ]
        }
      }
    ],
    "partialMatches": [],
    "targetCount": 1,
    "executablesCount": 1,
    "librariesCount": 0,
    "targets": [
      {
        "name": "tmp-esp32-cv-test",
        "type": "EXECUTABLE"
      }
    ]
  },
  "settings": [
    {
      "communicationMode": "automatic",
      "useCMakePresets": "auto",
      "configureOnOpen": true
    }
  ]
}

Debug Log

No response

Additional Information

Screenshots

Workaroud with set(CMAKE_CXX_FLAGS -fdiagnostics-color=always):

Task as shell command without fdiagnostics-color flag:

[bobbrow]

It seems that the way we are doing tasks removes the colors. Right now, if we were to send the commands directly to the terminal, we could get colors, but we also wouldn't be able to tell when the build completed or whether it succeeds or not. We'll need to talk to the VS Code team to see if they can give us more information from the Terminal object.

[piomis]

On my ArmClang, Windows 10 and VSCode Cmake Tools it looks to be working (I have it configured to useBuildTask)
.
When I add compiler setting: -fdiagnostics-color=always
it looks to be working when ArmClang called directly from shell. But not if I build with ninja and/or cmake (thus also VSCode CMake tools).

But when I add -fansi-escape-codes as compiler option it starts to be working also with ninja, cmake and in vscode termianal output.

Obviously these are only Clang colours. Ninja messages are still monochromatic.
As far as I managed to find out it is more ninja limitation which automatically disables colours when detecting to be called in "piped" way (and that is how cmake runs ninja).

[bobbrow]

I'm talking with the VS Code team about this issue: microsoft/vscode#145234. If we can move the implementation to run directly in the terminal, I think it will work the way you expect.

[moefear85]

for those waiting for salvation: vscode extensions->build output colorizer by steve bush.

[starball5]

@piomis yes. see Ninja Build System + gcc/clang doesn't output diagnostic colors

Also, more generally, How can I configure CMake to generate a buildsystem that emits colored errors and warnings?