On Tue, 2011-05-03 at 09:48 +0200, Stefano Lattarini wrote: > > The other thing I was thinking is that this feature might want to be > > enabled via a command-line argument. All the complex makefiles > > generated by automake, etc. for example cannot take advantage of this > > if you have to modify every makefile to add the special target. > > > > > Not completely true. A developer using Automake who wants to take > advantage of this feature could just add the line: > .PARALLELSYNC: > to his Makefile.am file(s). Automake's preprocessing policy is to > pass through the things it doesn't understand (or that are not > influential to it).
Sure, I realize that. But that only helps developers. I was thinking about users of open source software, building it on larger machines with -jN and wanted to get "clean" output when it fails. That's my situation: I have archived vanilla tarballs downloaded directly from the upstream sites, and I have a makefile that does all that's necessary (unpack them, configure, build, install, etc.) I certainly don't want to have to go modify the Makefile.am / Makefile.in files to get this feature enabled. Also apropos of nothing, I don't like this name :-). Maybe .OUTPUTSYNC or something would be better? PARALLELSYNC doesn't help understand what the feature does. -- ------------------------------------------------------------------------------- Paul D. Smith <psm...@gnu.org> Find some GNU make tips at: http://www.gnu.org http://make.mad-scientist.net "Please remain calm...I may be mad, but I am a professional." --Mad Scientist _______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
