[Dune] [#922] silent builds

[Dune]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#922 - silent builds
User who did this - Arne Morten Kvarving (akva)

----------
@christian: the problem is that the AM_SILENT_RULES need to be called right after AM_INIT_AUTOMAKE according to the documentation. if we wrap both these up in a m4, we could do what you propose. is this acceptable?

you can sort of do silent builds without, namely make -s (which would require an alias or a hack in dunecontrol). this only silences parts of the output though, namely the 'entering directory foo' bits. you still get the whole compilation line echoed. this can of course be handled by a stdout redirect, but then you completely lose the overview of which file is currently being processed. i'm also not certain when -s was introduced, and i'm not sure if it's supported in other makes than gnu make.

not really important; but if we wanted a solution that works with older automake's, a third option is to override the default %cpp.o (etc) rules, something ala https://github.com/xbmc/xbmc/blob/master/Makefile.include.in
----------

More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=922#comment2558

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.