[Top][All Lists]

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

Re: Feature request

From: Albert Chin
Subject: Re: Feature request
Date: Fri, 17 Sep 2004 08:27:54 -0500
User-agent: Mutt/1.5.6i

On Fri, Sep 17, 2004 at 10:50:09AM +0200, Andreas Schwab wrote:
> 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.

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.

albert chin (address@hidden)

reply via email to

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