-
Notifications
You must be signed in to change notification settings - Fork 35
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
Indicate clearly that building was successful #2
Comments
Thanks Tobychev, I am trying to optimize parallel compilations, after that I will improve the script CLI. |
Hi Tobychev, I have just improved the CLI (besides other improvements...); is it ok now? |
Hello szahi, sorry for taking so long with replying. I do like that the build settings are printed at the end of the build. However they are printed after the result of the build, so it is harder than it should be to see if a build succeed. I think the built result should be the very last thing printed before you return to the shell, after all the prompt is the only place guaranteed to end up on the screen of the user. |
Hi Tomas you are right. Monday I will change the CLI. Thank you
|
Hi Tomas, I have modified the CLI. Presently the build settings are the first message echoed, while the last is the ultimate, successful linked target. It is worthy of note that I have also tried to address the bug on capturing compilation error: now, if one file is not successfully compiled, FoBiS.py tracks it and the building ends immediately with a clear indication of which file has not been compiled. |
Hello Stefano, |
Currently building the example (using compiler=GNU), results in two lines being printed, the last one being a call to the compiler typeset in red. It is not obvious that this indicates a successful build.
The text was updated successfully, but these errors were encountered: