Indicate clearly that building was successful about fobis

[szaghi]

Thanks Tobychev,
you are right, it is better to be more verbose in some cases :-)

I am trying to optimize parallel compilations, after that I will improve the script CLI.

[szaghi]

Hi Tobychev,

I have just improved the CLI (besides other improvements...); is it ok now?

[Tobychev]

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.

[szaghi]

Hi Tomas you are right. Monday I will change the CLI. Thank you
Il 05/apr/2014 00:25 "Tomas Bylund" [email protected] ha scritto:

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.

Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-39617714
.

[szaghi]

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.

[Tobychev]

Hello Stefano,
thank you, this is clearer :)