This is the mail archive of the
automake@gnu.org
mailing list for the automake project.
Re: More fun with BUILT_SOURCES
- To: Tom Tromey <tromey at cygnus dot com>
- Subject: Re: More fun with BUILT_SOURCES
- From: Braden McDaniel <braden at endoframe dot com>
- Date: Sat, 25 Nov 2000 21:10:16 -0500 (EST)
- cc: Alexandre Oliva <oliva at lsd dot ic dot unicamp dot br>, <automake at gnu dot org>
- List-Id: Discussion list for automake <automake.gnu.org><mailto:automake-request@gnu.org?subject=unsubscribe>
On 25 Nov 2000, Tom Tromey wrote:
> >>>>> "Braden" == Braden McDaniel <braden@endoframe.com> writes:
>
> >> > I realize that BUILT_SOURCES is known to be problematic, but I haven't
> >> > found any other solution. Any suggestions?
>
> >> Add explicit dependencies on it. There's no other way to ensure it's
> >> generated. BUILT_SOURCES used to work only with GNU make.
>
> Braden> Each source file for my library depends on the generated
> Braden> header, directly or indirectly. Is it possible for me to add
> Braden> explicit dependencies *and* keep the libfoo_la_SOURCES
> Braden> variable? I'm trying to hang on to all of automake's benefits
> Braden> that I possibly can.
>
> You should be able to do that.
>
> I'd really like to find a better solution for the built files
> problem. This is currently too hard to do in automake.
I ended up doing this:
$(libfoo_la_OBJECTS): mybuiltheader.h
--
Braden N. McDaniel e-mail: braden@endoframe.com
<http://endoframe.com> Jabber: braden@jabber.com