Re: [wxhaskell-devel] wxWidgets 2.8.7 support

[Jeremy O'D. <je...@o-...>]

On Fri, 11 Apr 2008 09:29:48 +0100, "Eric Y. Kow" <eri...@gm...>
said:
> On Thu, Apr 10, 2008 at 15:12:50 +0100, Jeremy O'Donoghue wrote:
> > - wxWidgets 2.8.7 was compiled from source using Visual Studio 2008
> > (i.e. on Windows)
> 
> Great! Thanks!
> 
> ... but I get this compile error on MacIntel
> 
> g++ -c wxc/src/eljvalidator.cpp -o dist/wxc/eljvalidator.o -MD
> -DwxcREFUSE_MEDIACTRL -DwxcREFUSE_OPENGL
> -I/usr/local/lib/wx/include/mac-unicode-release-2.8
> -I/usr/local/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES
> -D__WXMAC__   -fPIC -Iwxc/include 
> wxc/src/eljvalidator.cpp: In function &#8216;void*
> wxTextValidator_GetIncludes(void*, int*)&#8217;: wxc/src/eljvalidator.cpp:159:
> error: &#8216;_wcsdup&#8217; was not declared in this scope
> wxc/src/eljvalidator.cpp: In function &#8216;void*
> wxTextValidator_GetExcludes(void*, int*)&#8217;: wxc/src/eljvalidator.cpp:192:
> error: &#8216;_wcsdup&#8217; was not declared in this scope
> make: *** [dist/wxc/eljvalidator.o] Error 1

Shelarcy got this one for me... we need to replace _wcsdup with
wxStrdup(). _wcsdup() is Microsoft specific.

> >   with the following options:
> >   - WXWIN_COMPATIBILITY_2_4 0
> >   - WXWIN_COMPATIBILITY_2_6 0
> >   - wxUSE_UNICODE 1
> >   - wxUSE_MEDIACTRL 1
> >   - wxUSE_XML 1
> >   - wxUSE_GLCANVAS 1
> >   - wxUSE_ODBC 1
> 
> How do I get the same listing?

I'm afraid this one was manual copy and paste. It would be very easy to
create a script to do it, though, and we should probably consider (as we
could then do autoconfig of wxHaskell build for Windows). All you need
to do is search wx/setup.h for the wxWidgets install in path.

The most important of the features above that we should consider further
is WXWIN_COMPATIBILITY_2_6 (which I disabled) - I could see (given
packaging time for e.g. Debian) a benefit in trying to support the
current and previous releases of wxWidgets. At the same time, I think
it's very important to maintain a close link between wxcore and
wxWidgets library itself - otherwise we would need to fully document
wxcore (at present the wxWidgets docs are quite useable as documentation
for wxcore, but if we don't keep up, they become less so over time.

Regards
Jeremy