[Top][All Lists]

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

Re: how to override precious variables for subdirs

From: Ralf Wildenhues
Subject: Re: how to override precious variables for subdirs
Date: Wed, 27 Apr 2011 08:15:46 +0200
User-agent: Mutt/1.5.20 (2010-08-04)

Hello Chris,

* Chris Frey wrote on Mon, Apr 25, 2011 at 09:28:51PM CEST:
> On Sat, Apr 23, 2011 at 12:13:13PM +0200, Ralf Wildenhues wrote:
> > It is possible to amend or modify $ac_configure_args from within the
> > toplevel configure (watch out with quoting, its contents are to be
> > eval'ed later), but that might mean you'd have to turn off config.cache.
> There is no API to do this, though, is there?

Not really.

> As I understand it,
> $ac_configure_args is just one long string containing the arguments.

Yes.  But they are quoted suitably to survive being eval'ed.  This
latter bit is important: you cannot analyze them either without using

> I did try to hack the individual $ac_env_PKG_CONFIG_PATH_value and
> $ac_cv_env_*_value variables, but the command line arguments for
> subdir processing seem to be generated before any user code.
> By the time my code runs, the arguments are set.


> > Incidentally, a patch has been proposed quite recently to add extra
> > arguments to (some) sub package configure invocations.  It is still
> > pending copyright assignment clearance before review, but definitely
> > interesting.  It might help you.  However, given the preciousness it
> > might also mean that an eventual config.cache file cannot be shared
> > between the different configure scripts.
> Where might I find this patch?  Maybe I could give it a try.

As I said, it wouldn't yet solve the config.cache issues with your
approach (so you shouldn't use -C with it for now).


reply via email to

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