diff options
| author | David Phillips <david@sighup.nz> | 2018-05-16 19:25:58 +1200 |
|---|---|---|
| committer | David Phillips <david@sighup.nz> | 2018-05-16 19:26:41 +1200 |
| commit | 39176a1d06dccae9340383f818a556df4cea3335 (patch) | |
| tree | f4af127b47fc91d57b8a1d27406649d50f3f3534 /README.md | |
| parent | ff5a11ed6d0eeb8ed449e923abf68bc603f41926 (diff) | |
| download | sand-leek-39176a1d06dccae9340383f818a556df4cea3335.tar.xz | |
Add compile-time flag to disable coloured output
Turns out windows builds run in plain powershell or cmd.exe display the
raw ANSI escape sequences rather than interpreting. No official support
for interpreting them that I can see.
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 5 |
1 files changed, 4 insertions, 1 deletions
@@ -34,7 +34,7 @@ platforms with both gcc and clang. Builds and tests have been successfully carried out for: -* Windows with MinGW on Linux +* Windows with MinGW on Linux - I cannot support coloured output for Windows * Solaris 10 but these are not automated, nor are they part of the primarily supported @@ -64,3 +64,6 @@ similar tools out there when pushing work across cores. ## Inspiration sand leek was greatly inspired by schallot, escahlot and scallion. +## Compile-time flags + +* `SAND_LEEK_DISABLE_COLOUR` - Don't compile in any support for coloured output. Recommended for Windows builds unless support can be had for ANSI escape sequences |