Re: Automatically Handling Tools that Produce Many Outputs

2007-12-10 Thread Robert Collins
On Mon, 2007-12-10 at 21:51 +, Olly Betts wrote: > > I can't think of a way to easily dig out statistically useful data > from a VCS or Google code search on how often it happens either to me > or > generally. But I mainly offered it as a more concrete example of the > sort of issues I had i

Re: Automatically Handling Tools that Produce Many Outputs

2007-12-10 Thread Olly Betts
On Wed, Nov 28, 2007 at 07:15:10PM +0100, Ralf Wildenhues wrote: > elc-stamp: $(elc_stamp_SOURCES) > @rm -f [EMAIL PROTECTED] > @touch [EMAIL PROTECTED] > $(elc_stamp_COMMAND) > @mv -f [EMAIL PROTECTED] $@ Hmm, what's the reason for "rm -f" before "touch" here? Cheers,

Re: Automatically Handling Tools that Produce Many Outputs

2007-12-10 Thread Olly Betts
On Mon, Dec 10, 2007 at 09:15:26AM +0100, Ralf Wildenhues wrote: > * Olly Betts wrote on Sun, Dec 09, 2007 at 03:53:11AM CET: > > On Wed, Nov 28, 2007 at 07:15:10PM +0100, Ralf Wildenhues wrote: > > > That would drive us > > > further away from being able to copy the contents of Makefile.am into >

Re: problem using the .a libs ...

2007-12-10 Thread Kamaljit Singh
The way the .a work is that if a undefined symbol is defined by a .o in the .a then only the .o is linked in otherwise it isnt linked in. But when you do *.o then you link in all .o's regardless. The .o's in the .a are evaluated as they are seen hence they'll not be revisited in case a later

Re: Automatically Handling Tools that Produce Many Outputs

2007-12-10 Thread Ralf Wildenhues
Hello Olly, * Olly Betts wrote on Sun, Dec 09, 2007 at 03:53:11AM CET: > On Wed, Nov 28, 2007 at 07:15:10PM +0100, Ralf Wildenhues wrote: > > * Olly Betts wrote on Tue, Nov 27, 2007 at 01:30:31AM CET: > > > > data.c data.h::: data.foo > > > foo data.foo > > > > Yuck. Let's bette