[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Special chars in arguments
From: |
Tim Van Holder |
Subject: |
Special chars in arguments |
Date: |
Fri, 2 Mar 2001 18:14:46 +0100 |
I'm still looking into fixing the sub-configure stuff.
If --srcdir or --cache-file contain shell metachars (as
they would on DOS systems, for example, as they use a
backslash as dirsep), they get quoted at the start of
configure (after option parsing is completed).
Because of this, the case statement at the start of
the sub-configure stuff doesn't recognize these options
and allows them to pile up. What's worse, they then pass
the srcdir and cache file settings to the sub-configure
unprotected.
IMHO, the cleanest way to solve this would be to change
the way special args are quoted. Instead of having
--foo --bar '--srcdir=C:\Stupid\Path\'
we could use
--foo --bar --srcdir='C:\Stupid\Path\'
Of course, this assumes that all args containing metachars
have them only in their option argument.
So my question is: can simple options also have shell
metachars in their names, or is this unsupported?
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Special chars in arguments,
Tim Van Holder <=