Re: `--prefix /foo' mishandled in sub-configure invocation

[Ralf Corsepius]

Am Die, 2001-11-06 um 12.44 schrieb Akim Demaille:
> >>>>> "Ralf" == Ralf Corsepius <address@hidden> writes:
> 
> Ralf> Just for clarification: Are you saying that --*dir foo
> 
> Yes.
> 
> Ralf> --[with|without]* foo --[enable|disable]* foo all are supported? 
> 
> No, these have *optional* arguments.
> 
> 
> Ralf> Therefore, this considering '--prefix foo' in argument parsing
> Ralf> results into basically different requirements on parsers [1] and
> Ralf> therefore must be documented (or officially deprecicated), IMHO.
> 
> Rather, I'd like to understand why you post-parse the arguments, since
> that's the actual bottom line.
Yep. I guess you know :-)

Working around deficiencies of my "favorite" friends:
AC_CONFIG_SUBDIRS and AC_ARG_VARS wrt. to deep packages and
Canadian-Cross support.

What I am doing basically is letting toplevel configure scripts set up
configure-script arguments, environment variables (CC etc) and build
directories (eg. --with-target-subdir) for several sub-packages,
processing canonicalization tripples, prefixes etc.
Another topic related to this is dynamically setting up config-subdirs
(Working around the "you should use literals"-issue).

Ralf