[SERVER-47115] Enable colorized compiler output for new ninja module Created: 25/Mar/20 Updated: 05/Sep/23 Resolved: 28/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Won't Fix | Votes: | 3 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Server Development Platform
|
||||||||
| Participants: | |||||||||
| Description |
|
The new ninja generator doesn't seem to set the right compiler flags to enable this output as it should. See this post, and also these lines from the old ninja module. As a workaround, you can add CCFLAGS="-fdiagnostics-color=always" |
| Comments |
| Comment by Mathias Stearn [ 04/Feb/21 ] |
|
Can we prioritize this? We shouldn't require everyone to need to know about that flag, or the arcane reasons why it is needed, in order to make it less painful to debug compile failures. |
| Comment by Andrew Morrow (Inactive) [ 06/Apr/20 ] |
|
Thanks charlie.swanson for the suggestion. As there is a straightforward workaround, I'm going to put this in the bucket of general build system improvements. |