This is the mail archive of the
automake@gnu.org
mailing list for the automake project.
Re: Feature request
Albert Chin <automake@mlists.thewrittenword.com> 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.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."