BuildSys - log checking

Hi, may I pass on a few suggestions for the BuildSys – basically due to oddities I was experiencing:

Checking the logs from any step is a bit work – especially since the ARM assembler outputs things like “0 Errors, 1 Warning” so that searching for error can take a lot of time. (Replacing “0 Errors” by “OK” is not a good idea since there is the risk that in some place there is “10 Errors”).

And the C compiler seems to even write more times “Error” since I see this the odd time: “2 warnings, 0 errors, 0 serious errors” – well those might be easier to take care of since as far as I was able to see that happens in case of implicit casts which can be fixed in the code.

Perhaps it is possible to kind of get return codes or such so that you can indicate at the end if there were any errors needing attention; or to ask the Assembler (any other tools) to not write “0 Errors” at all.

Or perhaps the tools can be asked to not write things like “0 errors” etc. at all, or then write “no errors” or such so that find/replace can be used easier – especially considering that ASM has “x errors, y warning” whereas cc writes “x warning, y errors, z serious errors”.

Thanks

Um, amu, link, objasm and cc do set the return code if there are errors or serious errors, unless it’s been changed in later years. It’s certainly relied on by AMU to ensure that it terminates when there is a problem.

If you’re manually running the tools in an obey file, check Sys$ReturnCode for the return code.

Currently (early phase) I try to familiarize myself with the BuildSys – and I do tend to use the Build App to run things (partially since that does set all paths and run the right things) – but since it runs many things in one go the logs are longish…
If I’d run the odd make file for one tool separately then that would not be a problem (as I ages ago did when I added duplex print to the PCL printer driver)