package/archlinux: enable colored compiler output in dev PKGBUILDs.

See the correspnding commit in Corrade for details.

package/archlinux/PKGBUILD

@@ -19,12 +19,19 @@ build() {
     cd "$_rootdir/build"
 
     # RelWithDebInfo is enabled but not built -- it's meant for profiling from
-    # within the build dir
+    # within the build dir.
+    #
+    # Colored output is enabled implicitly. If Ninja detects it's outputting to
+    # a pipe, it strips it away from the output, alternatively you can set the
+    # GCC_COLORS= (empty) env variable to temporarily disable colors. The
+    # inverse, i.e. preserving colors when Ninja outputs to a pipe can be done
+    # with CLICOLOR_FORCE=1: https://github.com/ninja-build/ninja/issues/2196
     cmake .. \
         -DCMAKE_CONFIGURATION_TYPES="Debug;Release;RelWithDebInfo" \
         -DCMAKE_CROSS_CONFIGS=all \
         -DCMAKE_CXX_FLAGS_RELWITHDEBINFO="-O2 -g -DNDEBUG -fno-omit-frame-pointer" \
         -DCMAKE_INSTALL_PREFIX=/usr \
+        -DCMAKE_COLOR_DIAGNOSTICS=ON \
         -DMAGNUM_WITH_AUDIO=ON \
         -DMAGNUM_WITH_VK=ON \
         -DMAGNUM_WITH_GLFWAPPLICATION=ON \

package/archlinux/PKGBUILD-android-arm64

@@ -28,8 +28,14 @@ build() {
 
     cd "$_rootdir/build-android-arm64"
 
+    # Colored output is enabled implicitly. If Ninja detects it's outputting to
+    # a pipe, it strips it away from the output; Clang unfortunately doesn't
+    # have any env var to temporarily disable colors. The inverse, i.e.
+    # preserving colors when Ninja outputs to a pipe can be done with
+    # CLICOLOR_FORCE=1: https://github.com/ninja-build/ninja/issues/2196
     cmake .. \
         -DCMAKE_BUILD_TYPE=Release \
+        -DCMAKE_COLOR_DIAGNOSTICS=ON \
         -DMAGNUM_WITH_VK=ON \
         -DMAGNUM_WITH_ANYAUDIOIMPORTER=OFF \
         -DMAGNUM_WITH_ANYIMAGECONVERTER=ON \

package/archlinux/PKGBUILD-coverage

@@ -22,10 +22,16 @@ build() {
     newcxxflags=$(echo $CXXFLAGS | sed s/-O.//g | sed s/-D_FORTIFY_SOURCE=.//g)
     export CXXFLAGS="$newcxxflags"
 
+    # Colored output is enabled implicitly. If Ninja detects it's outputting to
+    # a pipe, it strips it away from the output, alternatively you can set the
+    # GCC_COLORS= (empty) env variable to temporarily disable colors. The
+    # inverse, i.e. preserving colors when Ninja outputs to a pipe can be done
+    # with CLICOLOR_FORCE=1: https://github.com/ninja-build/ninja/issues/2196
     cmake .. \
         -DCMAKE_CXX_FLAGS="--coverage" \
         -DCMAKE_BUILD_TYPE=Debug \
         -DCMAKE_INSTALL_PREFIX=/usr \
+        -DCMAKE_COLOR_DIAGNOSTICS=ON \
         -DMAGNUM_WITH_AUDIO=ON \
         -DMAGNUM_WITH_VK=ON \
         -DMAGNUM_WITH_GLFWAPPLICATION=ON \

package/archlinux/PKGBUILD-emscripten-wasm

@@ -26,9 +26,16 @@ build() {
 
     # Put tests into a separate target as they take ages to build. They're
     # built only inside check() so `makepkg --nocheck` will skip building them.
+    #
+    # Colored output is enabled implicitly. If Ninja detects it's outputting to
+    # a pipe, it strips it away from the output; Clang unfortunately doesn't
+    # have any env var to temporarily disable colors. The inverse, i.e.
+    # preserving colors when Ninja outputs to a pipe can be done with
+    # CLICOLOR_FORCE=1: https://github.com/ninja-build/ninja/issues/2196
     cmake .. \
         -DCMAKE_BUILD_TYPE=Release \
         -DCMAKE_INSTALL_PREFIX=/usr/lib/emscripten/system \
+        -DCMAKE_COLOR_DIAGNOSTICS=ON \
         -DMAGNUM_DEPLOY_PREFIX=/srv/http/emscripten \
         -DMAGNUM_WITH_AUDIO=ON \
         -DMAGNUM_WITH_EMSCRIPTENAPPLICATION=ON \

package/archlinux/PKGBUILD-emscripten-wasm-webgl2

@@ -26,9 +26,16 @@ build() {
 
     # Put tests into a separate target as they take ages to build. They're
     # built only inside check() so `makepkg --nocheck` will skip building them.
+    #
+    # Colored output is enabled implicitly. If Ninja detects it's outputting to
+    # a pipe, it strips it away from the output; Clang unfortunately doesn't
+    # have any env var to temporarily disable colors. The inverse, i.e.
+    # preserving colors when Ninja outputs to a pipe can be done with
+    # CLICOLOR_FORCE=1: https://github.com/ninja-build/ninja/issues/2196
     cmake .. \
         -DCMAKE_BUILD_TYPE=Release \
         -DCMAKE_INSTALL_PREFIX=/usr/lib/emscripten/system \
+        -DCMAKE_COLOR_DIAGNOSTICS=ON \
         -DMAGNUM_DEPLOY_PREFIX=/srv/http/emscripten-webgl2 \
         -DMAGNUM_TARGET_GLES2=OFF \
         -DMAGNUM_WITH_AUDIO=ON \

package/archlinux/PKGBUILD-es2

@@ -17,9 +17,15 @@ build() {
     mkdir -p "$_rootdir/build-es2"
     cd "$_rootdir/build-es2"
 
+    # Colored output is enabled implicitly. If Ninja detects it's outputting to
+    # a pipe, it strips it away from the output, alternatively you can set the
+    # GCC_COLORS= (empty) env variable to temporarily disable colors. The
+    # inverse, i.e. preserving colors when Ninja outputs to a pipe can be done
+    # with CLICOLOR_FORCE=1: https://github.com/ninja-build/ninja/issues/2196
     cmake .. \
         -DCMAKE_BUILD_TYPE=Debug \
         -DCMAKE_INSTALL_PREFIX=/usr \
+        -DCMAKE_COLOR_DIAGNOSTICS=ON \
         -DMAGNUM_TARGET_GLES=ON \
         -DMAGNUM_TARGET_GLES2=ON \
         -DMAGNUM_WITH_AUDIO=ON \

package/archlinux/PKGBUILD-es2desktop

@@ -17,9 +17,15 @@ build() {
     mkdir -p "$_rootdir/build-es2desktop"
     cd "$_rootdir/build-es2desktop"
 
+    # Colored output is enabled implicitly. If Ninja detects it's outputting to
+    # a pipe, it strips it away from the output, alternatively you can set the
+    # GCC_COLORS= (empty) env variable to temporarily disable colors. The
+    # inverse, i.e. preserving colors when Ninja outputs to a pipe can be done
+    # with CLICOLOR_FORCE=1: https://github.com/ninja-build/ninja/issues/2196
     cmake .. \
         -DCMAKE_BUILD_TYPE=Debug \
         -DCMAKE_INSTALL_PREFIX=/usr \
+        -DCMAKE_COLOR_DIAGNOSTICS=ON \
         -DMAGNUM_TARGET_GLES=ON \
         -DMAGNUM_TARGET_GLES2=ON \
         -DMAGNUM_TARGET_EGL=OFF \

package/archlinux/PKGBUILD-es3

@@ -17,9 +17,15 @@ build() {
     mkdir -p "$_rootdir/build-es3"
     cd "$_rootdir/build-es3"
 
+    # Colored output is enabled implicitly. If Ninja detects it's outputting to
+    # a pipe, it strips it away from the output, alternatively you can set the
+    # GCC_COLORS= (empty) env variable to temporarily disable colors. The
+    # inverse, i.e. preserving colors when Ninja outputs to a pipe can be done
+    # with CLICOLOR_FORCE=1: https://github.com/ninja-build/ninja/issues/2196
     cmake .. \
         -DCMAKE_BUILD_TYPE=Debug \
         -DCMAKE_INSTALL_PREFIX=/usr \
+        -DCMAKE_COLOR_DIAGNOSTICS=ON \
         -DMAGNUM_TARGET_GLES=ON \
         -DMAGNUM_TARGET_GLES2=OFF \
         -DMAGNUM_WITH_AUDIO=ON \

package/archlinux/PKGBUILD-es3desktop

@@ -17,9 +17,15 @@ build() {
     mkdir -p "$_rootdir/build-es3desktop"
     cd "$_rootdir/build-es3desktop"
 
+    # Colored output is enabled implicitly. If Ninja detects it's outputting to
+    # a pipe, it strips it away from the output, alternatively you can set the
+    # GCC_COLORS= (empty) env variable to temporarily disable colors. The
+    # inverse, i.e. preserving colors when Ninja outputs to a pipe can be done
+    # with CLICOLOR_FORCE=1: https://github.com/ninja-build/ninja/issues/2196
     cmake .. \
         -DCMAKE_BUILD_TYPE=Debug \
         -DCMAKE_INSTALL_PREFIX=/usr \
+        -DCMAKE_COLOR_DIAGNOSTICS=ON \
         -DMAGNUM_TARGET_GLES=ON \
         -DMAGNUM_TARGET_GLES2=OFF \
         -DMAGNUM_TARGET_EGL=OFF \