-
-
Notifications
You must be signed in to change notification settings - Fork 22k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add colors to SCons error/warning messages #88074
Add colors to SCons error/warning messages #88074
Conversation
772d35b
to
37cef60
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pretty!
37cef60
to
0fcefaf
Compare
This also includes various improvements to the messages: - Remove some "success" messages that were printed on every build, such as the macOS minimum supported version (which is already mentioned in the documentation). Only the "error" variants of these messages are kept. - Use gray color for the build timer printed at the end of each build, and only display 2 decimals. - Use non-zero exit codes when exiting after some error messages that previously exited with a zero (success) exit code. - Improve formatting of the Direct3D 12 missing dependencies message. - Clarify how MSVC is detected in the message printed when it's detected. - Force colored output on CI (it's non-interactive but can still display colors).
0fcefaf
to
8064491
Compare
+ get_ndk_version() | ||
+ " manually." | ||
) | ||
sys.exit() | ||
sys.exit(200) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why 200
here specifically? We seem to use 255
throughout otherwise.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah I see we had this:
platform/windows/detect.py
305: sys.exit(200)
That's the only occurrence, so I'd tend to say it was a mistake and not an intentional error reporting API.
Superseded by #91220. |
This also includes various improvements to the messages:
Preview
I also had automatic underlining of backticked text at some point, but I removed it for now. Let me know if you'd like me to readd it: