Peter Williams <[EMAIL PROTECTED]> writes:
> So if we expect the user to have the tool, put them in $builddir, and if
> not, put them in $srcdir?
Basically, yes.
> Will automake find the built sources if I put them in $srcdir?
Yeah, it should just use vpath.
> 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?
I'm not familiar with balsa (or gob for that matter) so I'm not sure
exactly what's happening here? Is gob creating it's output file in
the same directory as it found ths source file?
/assar
