After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 586809 - Enable "silent rules" automake 1.11 option
Enable "silent rules" automake 1.11 option
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: general
2.28.x (obsolete)
Other Linux
: Normal enhancement
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
evolution[cleanup]
Depends on:
Blocks:
 
 
Reported: 2009-06-24 03:27 UTC by H.Habighorst
Modified: 2013-09-13 01:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28

Attachments
Add shave to evo ( except shave.in / shave-libtool.in ) (4.45 KB, patch)
2009-06-24 03:27 UTC, H.Habighorst 		rejected Details | Review
AM Silent Rules Macro activated (425 bytes, patch)
2009-06-24 12:33 UTC, H.Habighorst 		committed Details | Review

Description H.Habighorst 2009-06-24 03:27:05 UTC 
See http://live.gnome.org/GnomeGoals/NicerBuilds .

This is not yet approved, yes - but shave is really nice, especially for evolution where a lot of output is generated.

There are two files which must be added to evolution, shave.in and shave-libtool.in .

The patch appended does the rest. Have Fun.

Before should bug 586806 be closed, otherwise you'll get /include errors.
Comment 1 H.Habighorst 2009-06-24 03:27:56 UTC 
Created attachment 137283 [details] [review]
Add shave to evo ( except shave.in / shave-libtool.in )
Comment 2 Daniel Macks 2009-06-24 03:58:21 UTC 
For an alternative solution to the build-verbiage, just toss 

m4_ifdef([AM_SILENT_RULES],[AM_SILENT_RULES([yes])])

into configure.ac and make sure you have automake1.11 when you regenerate the autotool scripts.
Comment 3 H.Habighorst 2009-06-24 04:08:23 UTC 
I know it's possible to do this - but as far as I know automake 1.11 was released this year.

I didn't want to do this because I think it's too new.

But if the devs say it's wanted, it wouldn't be impossible to do this... :)
Comment 4 Matthew Barnes 2009-06-24 04:20:52 UTC 
The new automake 1.11 macro is supposed to be backward-compatible with older automake versions (which I assume means ignored if not supported).  I'd rather go that route than add yet another build tool to the existing mess.
Comment 5 Daniel Macks 2009-06-24 04:27:03 UTC 
Yes, if you autogenerate with an automake < 1.11, the "quiet the build" feature simply won't be available and building will proceed exactly as it does now. That's what the m4_ifdef wrapper does: simply omits using the macro if the macro (which implements the quiet mode and is present in automake as of 1.11) is not available.
Comment 6 H.Habighorst 2009-06-24 12:33:38 UTC 
Created attachment 137307 [details] [review]
AM Silent Rules Macro activated

Okay, convinced. The added patch does the following and obsoletes the shave patch.