You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, not all GCC errors are printed at the error level to the cmd line. Often, just a generic error message (Compiler #error) is printed and the user must go into the build log to find the actual error and the failing line info. This is not the expected experience as most build environments dump this info at the cmd line.
Describe the solution
Print the GCC error info including line numbers and actual errors at the build cmd line.
Have you considered any alternatives?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
What does the feature solve?
Currently, not all GCC errors are printed at the error level to the cmd line. Often, just a generic error message (Compiler #error) is printed and the user must go into the build log to find the actual error and the failing line info. This is not the expected experience as most build environments dump this info at the cmd line.
Describe the solution
Print the GCC error info including line numbers and actual errors at the build cmd line.
Have you considered any alternatives?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: