Re: [lmi] Using 'wx-config' with zsh

[Greg Chicares]

I think wx-2.7 has solved this problem with zsh; Wendy, would you
confirm that, please? Would you please test it with the two msw
ports of ash that I've traditionally used to check portability:
  - cygwin's 'sh.exe'
  - Mikey's "self hosting" ash from ftp.franken.de [jfgi]
as well? I'd like to simplify the makefiles by using 'wx-config',
but want to know the ramifications. I don't think we'll be able
to upgrade to wx-2.7 for the April release, so this can wait a
few weeks if necessary.

On 2006-3-19 17:33 UTC, Greg Chicares wrote:
> In our office, we customarily use an msw port of an old version
> of zsh. It won't execute 'wx-config':
> 
> C:/wxWidgets-2.6.2/build_3_4_2[0]$echo $ZSH_VERSION
> 3.0.5-nt-beta-0.75
> C:/wxWidgets-2.6.2/build_3_4_2[0]$./wx-config
> printf: not found
> printf: not found
> C:/wxWidgets-2.6.2/build_3_4_2[1]$
> 
> It seems odd that 'printf' is used in a script that needs to be
> portable. The hash-bang is "#!/bin/sh", but 'printf' was added
> to zsh between versions 4.0 and 4.2:
>   http://zsh.sunsite.dk/releases.html
> Of course, we could use cygwin's port of zsh, which is at least
> version 4.2.4, but
>  - we shouldn't need to, just to run one nonportable script
>  - cygwin's isn't native, so it might be slower
>  - changing any tool is risky
> 
> However, extracting the one crucial line from 'wx-config':
>   lib/wx/config/msw-ansi-release-2.6
> gives us all I think we need--i.e., '--cxxflags' and '--libs':
> 
> C:/wxWidgets-2.6.2/build_3_4_2[0]$lib/wx/config/msw-ansi-release-2.6 
> --cxxflags
> -I/usr/local/lib/wx/include/msw-ansi-release-2.6 -I/usr/local/include/wx-2.6 
> -D_
> _WXMSW__ -DWXUSINGDLL=1 -DNO_GCC_PRAGMA
> C:/wxWidgets-2.6.2/build_3_4_2[0]$lib/wx/config/msw-ansi-release-2.6 --libs
> -L/usr/local/lib   -Wl,--subsystem,windows -mwindows -lwx_msw-2.6