>>>>> "Guido" == Guido Draheim <[EMAIL PROTECTED]> writes:
Guido> As the discussion does now lead a bit elsewhere, what about
Guido> second-level options, settable via VAR=VAL (or sth. alike)?
Guido> There was the discussion that for cross-compiling, people do
Guido> often have the needs to preset variables that are later stored
Guido> in the config.cache (e.g. ac_cv_bigendian), but nobody really
Guido> knows their name until they read the configure source code. May
Guido> be its worth to support sth. like AC_OPTVAR(varname, helptext),
Guido> and the variable/helptext would not be shown unless called with
Guido> an extra option --help-vars (or sth. alike), and on the main
Guido> helpscreen, just add a line saying that VAR=VAL is supported
Guido> and the exported varlist can be seen with another help call.
Guido> By the way, the explicit AC_OPTVAR is not actually needed for
Guido> the heap of macros that do AC_CHECK_CACHE - they have the
Guido> varname/msgtext relation already in place, just need a generic
Guido> way to export it to the local commandline user (or those who
Guido> run `configure` from a GUI-wrapper).
See AC_ARG_VAR.
