From: Paul Smith psm...@gnu.org
Cc: stefano.lattar...@gmail.com, bug-make@gnu.org
Date: Thu, 02 May 2013 16:21:36 -0400
The one and only difference between them is that when running a
recursive make, -Otarget WILL NOT capture the output of the sub-make,
leaving whatever it prints going to
On Fri, 2013-05-03 at 09:50 +0300, Eli Zaretskii wrote:
From: Paul Smith psm...@gnu.org
Cc: stefano.lattar...@gmail.com, bug-make@gnu.org
Date: Thu, 02 May 2013 16:21:36 -0400
The one and only difference between them is that when running a
recursive make, -Otarget WILL NOT capture the
Reading this discussion, as a bystander I can't help wondering whether
the addition of -O is worthwhile. Unix tools are supposed to be
small and dedicated. Using a separate utility seems to be a clean
solution here, and that is fact how it was originally done:
From: Paul Smith psm...@gnu.org
Cc: stefano.lattar...@gmail.com, bug-make@gnu.org
Date: Fri, 03 May 2013 07:47:09 -0400
The way the user experiences the -Ojob option's results is that the
output of every line of each recipe is dumped as soon as that line is
complete.
I would suggest
From: Paul Smith psm...@gnu.org
Date: Fri, 03 May 2013 08:57:57 -0400
Cc: bug-make@gnu.org
I think having this facility built into make is a win, especially as
parallel builds become predominant. I would be even more happy about it
if we can get it to the point where it can be enabled by
I've done the external utility solution and only because we absolutely
had no other choice - it's not much fun and can be done much more
effectively by make itself.
Regards,
Tim
On 3 May 2013 14:16, Eli Zaretskii e...@gnu.org wrote:
From: Paul Smith psm...@gnu.org
Date: Fri, 03 May 2013
From: Paul Smith psm...@gnu.org
Cc: stefano.lattar...@gmail.com, bug-make@gnu.org
Date: Fri, 03 May 2013 09:08:27 -0400
You're concentrating on the one recursive make target and saying
this doesn't follow the rule, while I'm concentrating on all
targets in the sub-make and saying let's
I have a solution for this problem that I think will work well, and will
be simple to implement.
Suppose we do this: if we're about to invoke a line marked recursive and
we're in -Otarget mode, then before we run it we'll show the current
contents of the temp file (using the normal synchronized
