On Wed, 25 Feb 2009, Ralf Wildenhues wrote:
> * Allan Caffee wrote on Wed, Feb 25, 2009 at 12:43:02AM CET:
> > Although I must admit I'm not sure what he means by
> > > > [...] this shouldn't matter for read-only trees iff your
> > > > dependencies are set up correctly [...]
> > I'm not really sur
* Allan Caffee wrote on Wed, Feb 25, 2009 at 12:43:02AM CET:
> Although I must admit I'm not sure what he means by
> > > [...] this shouldn't matter for read-only trees iff your
> > > dependencies are set up correctly [...]
> I'm not really sure how else you could have generated.c on the source
>
On Mon, 23 Feb 2009, Tavian Barnes wrote:
> 2009/2/23 Ralf Wildenhues :
> [...]
> > generated.c can live in the source or in the build tree. But given that
> > different make implementations have slightly different VPATH semantics,
> > it may be useful to require it to always live in the source tr
2009/2/23 Ralf Wildenhues :
> Hello Tavian,
>
> * Tavian Barnes wrote on Mon, Feb 23, 2009 at 06:22:12AM CET:
>> EXTRA_PROGRAMS = generate
>> generate_SOURCES = generate.c
>>
>> generated.c: generate
>
> BTW, the prerequisite here would need to be generate$(EXEEXT).
Oh, right.
>> ./genera
Hello Tavian,
* Tavian Barnes wrote on Mon, Feb 23, 2009 at 06:22:12AM CET:
> EXTRA_PROGRAMS = generate
> generate_SOURCES = generate.c
>
> generated.c: generate
BTW, the prerequisite here would need to be generate$(EXEEXT).
> ./generate$(EXEEXT) >$@
>
> bin_PROGRAMS = lookup
> lookup_
I have a project which auto-generates some look-up tables when checked
out from its SCM, and are distributed in the tarballs. These tables
used to be made by shell scripts called from autogen.sh, but I
recently ported them to C for a massive speed improvement. I've
implemented the Makefile.am lik