[wx-dev] Re: backward incompatible change to wx-config

[Vadim Zeitlin]

On Mon, 28 Jan 2008 09:59:50 +0100 Vaclav Slavik <vslavik at fastmail.fm> wrote:

VS> Vadim Zeitlin wrote:
VS> >  I thought it was a pity to remove this as this check is still
VS> > useful so I've checked in a slightly different fix which is
VS> > supposed to only ignore the extra parameters silently after
VS> > "--version". This should work with configure scripts generated
VS> > using 2.8 wxwin.m4 (could anyone please test this?)
VS> 
VS> I just did and no, it doesn't work. This configure.in code:
VS> 
VS>   AM_OPTIONS_WXCONFIG
VS>   AM_PATH_WXCONFIG([2.8.0],
VS>                    [WXFOUND=1], [WXFOUND=0],
VS>                    [xrc,html,xml,adv,core], [--unicode])
VS> 
VS> produces this configure code:
VS> 
VS>   WX_CONFIG_WITH_ARGS="$WX_CONFIG_PATH $wx_config_args --unicode 
VS> xrc,html,xml,adv,core"
VS>   WX_VERSION=`$WX_CONFIG_WITH_ARGS --version 2>/dev/null`
VS> 
VS> And this doesn't work, because --version is the last argument and the 
VS> check still fails.

 Maybe we could check whether the command line ends with "--version" (and
give an error if it doesn't) if we get an "unattached" parameter then? This
shouldn't be much more difficult (although I won't try to do it blindly
this time...) and will still allow us to detect incorrect usage.

VS> (BTW, is there some standard way of writing to config.log?

 From wx-config? I don't think so... I guess we could have wx-config.log
which would be created if some WX_CONFIG_LOG variable is set (we'd need to
mention it in the error message as otherwise nobody would find it, of
course). From configure itself it's just "echo 'to config log'>&5".

 Regards,
VZ