On Sat, 20 May 2000 21:09:55 Assar Westerlund wrote:
> Peter Williams <[EMAIL PROTECTED]> writes:
> > Do built sources go in $srcdir or $builddir?
>
> They should go in $builddir. Having a read-only $srcdir while
> building should be possible.
>
> > The automake rules for lex et al want to put the sources in
> > $builddir, but it seems that 'make dist' expects them to be in
> > $srcdir.
>
> I think that the theory behind this is that this is supposed to be
> made into a tar-ball, and therefore it should include all files. And
> besides, it's the maintainer doing this and therefore $srcdir should
> be writable.
>
So if we expect the user to have the tool, put them in $builddir, and if
not, put them in $srcdir? Will automake find the built sources if I
put them in $srcdir? Cause rightnow, when I build Balsa with a $srcdir
of '../balsa', I get:
gob --no-private-header ../../balsa/libinit_balsa/balsa-druid-page-finish.gob
cd .. \
&& CONFIG_FILES=libinit_balsa/Makefile CONFIG_HEADERS= /bin/sh ./config.status
creating libinit_balsa/Makefile
gcc -DHAVE_CONFIG_H -.... -c balsa-initdruid.c
gcc -DHAVE_CONFIG_H -.... -c balsa-druid-page-finish.c
gcc -DHAVE_CONFIG_H -.... -c ../../balsa/libinit_balsa/helper.c
Where 'gob' is the GTK object builder, which generates GTK+ object sources
and hooks up all the signals and stuff automagically. (It's pretty nice). Now
it would be pretty easy to put "(cd $(builddir) && gob $<)" in my make rule...
but then will automake prefix the '../../balsa/libinit_balsa' as it should?
--
==============================
Peter Williams [EMAIL PROTECTED]
"AIIEEEEEEEEE!!! DEATH ANTS!!"
