That has to do with the way the config.w32 files are processed.
changing one line in win32\build\buildconf.js from
re = new RegExp("(ARG_(ENABLE|WITH)([^;]+);)", "gm");
to
re = new RegExp("^(ARG_(ENABLE|WITH)([^;]+);)", "gm");
will prevent this from happening. This change will require the ARG_ to
start a the begining of the line.
Unless there are any reasons not to do this, I'll commit the patch.
- Frank
I had this in a config.w32 file:
ARG_ENABLE("winbinder", "winbinder support", "no");
//ARG_WITH("winbinder", "winbinder support", "no");line 2 is not treated as comment and after buildconf
cscript configure.js --help
both --enable-winbinder and --with-winbinder
were listed as availabe options.Don't know if this is a bug.
Davide.
Frank M. Kromann wrote:
That has to do with the way the config.w32 files are processed.
changing one line in win32\build\buildconf.js from
re = new RegExp("(ARG_(ENABLE|WITH)([^;]+);)", "gm");
to
re = new RegExp("^(ARG_(ENABLE|WITH)([^;]+);)", "gm");
will prevent this from happening. This change will require the ARG_ to
start a the begining of the line.
No need for such a requirement. I don't know whether the JS regex is
PCRE or not, but I believe something like this will solve that issue...
re = new RegExp("^\s*(ARG_(ENABLE|WITH)([^;]+);)", "gm");
-Stut