This is the mail archive of the
automake@gnu.org
mailing list for the automake project.
Re: More fun with BUILT_SOURCES
- To: Braden McDaniel <braden at endoframe dot com>
- Subject: Re: More fun with BUILT_SOURCES
- From: Tom Tromey <tromey at cygnus dot com>
- Date: 25 Nov 2000 18:49:46 -0700
- 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>
- References: <Pine.LNX.4.21.0011141018130.1056-100000@marrow.endoframe.com>
- Reply-To: tromey at cygnus dot com
>>>>> "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.
Tom