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
having tmp files is good for things to forget, but for error logs might be a good idea to keep them around.
compile messages are not always useless but everything is a bit too much.
I would save all messages to the compilscripts folder. For that I found a good solution on the web. I tried to adapt to be smaller, but It didn't quite work so I leave it as I found it
Get script directory
scriptDir="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
Log errors
make -j$numCores 2>> $project_error.log
Log everything
make -j$numCores 1>> /tmp/$project_log.log 2>> $scriptDir/$project_error.log
That logs in a very basic way. Maybe a developer could help us get a better solution.
The text was updated successfully, but these errors were encountered:
having tmp files is good for things to forget, but for error logs might be a good idea to keep them around.
compile messages are not always useless but everything is a bit too much.
I would save all messages to the compilscripts folder. For that I found a good solution on the web. I tried to adapt to be smaller, but It didn't quite work so I leave it as I found it
scriptDir="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
make -j$numCores 2>> $project_error.log
make -j$numCores 1>> /tmp/$project_log.log 2>> $scriptDir/$project_error.log
That logs in a very basic way. Maybe a developer could help us get a better solution.
The text was updated successfully, but these errors were encountered: