Hi Albert, Albert Chin wrote: > On Fri, Sep 17, 2004 at 10:50:09AM +0200, Andreas Schwab wrote: > >>Albert Chin <[EMAIL PROTECTED]> writes: >> >> >>>When building software with installable .m4 files (libtool, pkgconfig, >>>gtk+, etc.), if each software program is installed to a separate >>>directory, aclocal must be used like so: >>> $ aclocal -I [path to libtool .m4 files] \ >>> -I [path to pkgconfig .m4 files] ... >>> >>>How about an environment variable that aclocal would query that does >>>the job of -I? pkgconfig uses the PKG_CONFIG_PATH variable giving >>>locations for pkg-config to query for .pc files. Doing something >>>similar with aclocal would make automating use of aclocal in build >>>scripts much easier. >> >>Put the options in ACLOCAL_AMFLAGS in the toplevel Makefile.am and >>autoreconf will take care of everything. > > > Thanks. However, I prefer a solution where I didn't have to modify the > source if I modified the scripts used to build the software.
It may be small consolation, but the next release of GNU m4 has the last
bit of functionality required to eliminate aclocal entirely.
Cheers,
Gary.
--
Gary V. Vaughan ())_. [EMAIL PROTECTED],gnu.org}
Research Scientist ( '/ http://tkd.kicks-ass.net
GNU Hacker / )= http://www.gnu.org/software/libtool
Technical Author `(_~)_ http://sources.redhat.com/autobook
signature.asc
Description: OpenPGP digital signature
