On Mon, Jul 14, 2008 at 1:12 PM, Moritz Hoffmann <[EMAIL PROTECTED]> wrote:
> already some time ago I had a look at the build scripts oorexx uses on *nix > platforms. The primary motivation was to make the building look cleaner by > reducing the amount of messages written during compiling. Moritz, I like the idea of reducing some of the messages if you can. David is the expert here, so I'll defer to what he thinks. For the Linux kernel build, they have reduced the messages so that you normally just see CC and the name of the file being compiled, plus any warnings if there are any. Raven:/work/rigel/denx/linux-2.6-denx # make uImage CHK include/linux/version.h CHK include/linux/utsrelease.h ... CC mm/thrash.o CC mm/dmapool.o CC mm/shmem.o CC mm/slub.o LD mm/built-in.o CC fs/partitions/check.o fs/partitions/check.c: In function 'add_partition': fs/partitions/check.c:381: warning: ignoring return value of 'device_add', declared with attribute warn_unused_result But, they also have a switch you can use so that you can see everything if you want. That would be cool to have. <grin> -- Mark Miesfeld ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
