Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Wrong messages in "Build messages"
iw2nhl:
--- Quote from: killerbot on July 28, 2006, 03:40:44 pm ---I just checked and indeed in the build log it says in red : "Process terminated with status 1". So it show some indication of error.
--- End quote ---
That message is shown in "Build log", while my patch was for "Build messages", they are different tabs!
--- Quote from: killerbot on July 28, 2006, 03:40:44 pm ---On the other hand maybe we should stick with this, since we are not sure if every return type !=0 is indeed an indication of an error.
--- End quote ---
This rule should be valid for any command-line program, at least in Unix it's like that. Since most of the tools we use (MinGW tools) are ported from linux, this should be a good rule.
killerbot:
--- Quote from: iw2nhl on July 28, 2006, 09:16:39 pm ---
--- Quote from: killerbot on July 28, 2006, 03:40:44 pm ---I just checked and indeed in the build log it says in red : "Process terminated with status 1". So it show some indication of error.
--- End quote ---
That message is shown in "Build log", while my patch was for "Build messages", they are different tabs!
--- Quote from: killerbot on July 28, 2006, 03:40:44 pm ---On the other hand maybe we should stick with this, since we are not sure if every return type !=0 is indeed an indication of an error.
--- End quote ---
This rule should be valid for any command-line program, at least in Unix it's like that. Since most of the tools we use (MinGW tools) are ported from linux, this should be a good rule.
--- End quote ---
Well : build messages is primarly used for messages of the build which allow you to click on so you end up in the offending code. When I did my test build the focus was on the build log and it was very obvious something was wrong (red line ) ;-)
But then again you said, it was already fixed ... ??? and the patch was no longer needed.
I've learned that cvs can return !=0 although no error : cvs diff
Ok, cvs is not a build command but could be part of an automated thing, let's keep it in mind and think a little bit more about it.
iw2nhl:
--- Quote from: killerbot on July 28, 2006, 10:41:54 pm ---Well : build messages is primarly used for messages of the build which allow you to click on so you end up in the offending code. When I did my test build the focus was on the build log and it was very obvious something was wrong (red line ) ;-)
--- End quote ---
This was not my case: the focus was on "Build messages" and not on "Build log" and it showed that there were no errors at all. This was a bug.
--- Quote from: killerbot on July 28, 2006, 10:41:54 pm ---But then again you said, it was already fixed ... ??? and the patch was no longer needed.
--- End quote ---
Yes, now it find correctly that there is an error, so it has been fixed.
I don't know how it recognizes the error. Moreover I did not see changes about this in the changelog of last nigthly build... Either it was not listed or it has been a collateral effect of other changes.
--- Quote from: killerbot on July 28, 2006, 10:41:54 pm ---I've learned that cvs can return !=0 although no error : cvs diff
Ok, cvs is not a build command but could be part of an automated thing, let's keep it in mind and think a little bit more about it.
--- End quote ---
Nice, then we have no way to find errors?
Navigation
[0] Message Index
[*] Previous page
Go to full version