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
Typically the sort of error you'd see compiling a C++ project on Linux using Ninja for example would look like something similar to this:
FAILED: file.cpp.o
/usr/bin/g++ --all --flags --and --arguments --used
/path/to/file.cpp: in function someFunction():
exactFunction.containingError()
^~~~~~~~~~~~~~~~^
More often than not the compiler command is both huge and not useful to me, so I'd like an option to turn it off somehow. It can be incredibly noisy and makes it difficult to scan for compilation errors.
I couldn't find any documentation about this, and the --quiet flag does not do what I want.
For comparison, Make by default skips the compiler command, and only shows it if VERBOSE/V is set in any way.
The text was updated successfully, but these errors were encountered:
Typically the sort of error you'd see compiling a C++ project on Linux using Ninja for example would look like something similar to this:
More often than not the compiler command is both huge and not useful to me, so I'd like an option to turn it off somehow. It can be incredibly noisy and makes it difficult to scan for compilation errors.
I couldn't find any documentation about this, and the
--quiet
flag does not do what I want.For comparison, Make by default skips the compiler command, and only shows it if VERBOSE/V is set in any way.
The text was updated successfully, but these errors were encountered: