[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Feature request

From: Andreas Schwab
Subject: Re: Feature request
Date: Fri, 17 Sep 2004 10:50:09 +0200
User-agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3.50 (gnu/linux)

Albert Chin <address@hidden> 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 and
autoreconf will take care of everything.


Andreas Schwab, SuSE Labs, address@hidden
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."

reply via email to

[Prev in Thread] Current Thread [Next in Thread]