>>>>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Jean-Marc Lasgouttes wrote: CONFIGURE="../configure
Angus> --disable-debug
>> Useless on release version
Angus> I'm not building a release versionn just yet. AFAICT.
What I care about is to have a minimal configure command line for
people compiling a release. Ideally, "./configure" should be enough.
Angus> --with-frontend=qt
>> This is the default with 1.4.0cvs
Angus> N/A here.
Sure, but see above.
Angus> --with-qt-dir='${QT_DIR}'"
>> Useless.
Angus> No it's not. QT_DIR is not some global variable; it is defined
Angus> by my configure wrapper. Passing this data to the configure
Angus> script means that the location is hard-coded into the
Angus> Makefiles.
So you mean that QT_DIR should be changed to be a precious variable,
right?
-- Macro: AC_ARG_VAR (VARIABLE, DESCRIPTION)
Declare VARIABLE is a precious variable, and include its
DESCRIPTION in the variable section of `./configure --help'.
Being precious means that
- VARIABLE is `AC_SUBST''d.
- The value of VARIABLE when `configure' was launched is saved
in the cache, including if it was not specified on the command
line but via the environment. Indeed, while `configure' can
notice the definition of `CC' in `./configure CC=bizarre-cc',
it is impossible to notice it in `CC=bizarre-cc ./configure',
which, unfortunately, is what most users do.
We emphasize that it is the _initial_ value of VARIABLE which
is saved, not that found during the execution of `configure'.
Indeed, specifying `./configure FOO=foo' and letting
`./configure' guess that `FOO' is `foo' can be two very
different runs.
- VARIABLE is checked for consistency between two `configure'
runs. For instance:
$ ./configure --silent --config-cache
$ CC=cc ./configure --silent --config-cache
configure: error: `CC' was not set in the previous run
configure: error: changes in the environment can compromise \
the build
configure: error: run `make distclean' and/or \
`rm config.cache' and start over
and similarly if the variable is unset, or if its content is
changed.
- VARIABLE is kept during automatic reconfiguration (*note
config.status Invocation::) as if it had been passed as a
command line argument, including when no cache is used:
$ CC=/usr/bin/cc ./configure undeclared_var=raboof --silent
$ ./config.status --recheck
running /bin/sh ./configure undeclared_var=raboof --silent \
CC=/usr/bin/cc --no-create --no-recursion
JMarc
