Claus Reinke wrote:
?? Why would you give up on wxHaskell? :-) Seriously, if you
have real problems, please tell me so and we can see what
to do about it.

well, our problem was that no one was even listening to
the problems we told you about!-)
Hmm, maybe this was related that I was accidently unsubscribed
from this list for a few months.. :-(  Well, hopefully I'll listen
better from now on. However, I will have little time till October,
afterwards I'll be doing more development work again.
Hmm, when I do "ghc --version" it says:
The Glorious Glasgow Haskell Compilation System, version 6.4
I guessed tis means 6.4.0 and that 6.4.1 is the current
development version of ghc. I plan to only release binary
versions for stable versions of ghc -- people with development
versions of ghc are usually able to build wxHaskell themselves.

The latest development version of GHC works out of the box
with wxHaskell as it has real bugfixes that fix the current
problems on windows (while my bugfix release works around it).

Sigbjorn has set up nightly builds of both HEAD and STABLE
for mingw, and has merged the fixes to the STABLE branch while
bumping the version number to 6.4.1. So, windows ghc users are
no longer poor cousins, and can get the benefits of bug-fixes
without going for development builds (which are somewhere in
the 6.5 region) or waiting for infrequent releases. no need for
ugly work-arounds;-)

as for being able to build wxhaskell themselves, I'm in the process
of giving that a go (windows xp with cygwin and mingw,ghc-6.4.1,,wxWidgets 2.6.0+2 patches). wxWidgets
seems to have built and installed just fine, and ./configure for
wxHaskell works, but when trying to make wxHaskell, I get the
error below. Any suggestions?
First of all, I strongly recommend wxWidgets 2.4.2 since it is the only
version that works with ghci. Newer wxWidgets version use static
initializers that are not properly desctructed when the dynamic
link library is not re-loaded. Furthermore, there doesn't seem to
be that many new features useful on Windows.

g++ -c wxc/src/treectrl.cpp -o
out/wxc/treectrl.o -MD -IC:/cygwin/usr/local/include -IC:/cygwin/usr/local/lib/wx/include/msw-ansi-release-static-2.6 -I
C:/cygwin/usr/local/include/wx-2.6 -D__WIN95__ -D__WXMSW__ -Iwxc/include
wxc/src/treectrl.cpp: In function `void wxTreeCtrl_GetFirstChild(void*, void*,
   void*, void*)':
wxc/src/treectrl.cpp:333: warning: `GetFirstChild' is deprecated (declared at
wxc/src/treectrl.cpp: In function `void wxTreeCtrl_GetNextChild(void*, void*,
   void*, void*)':
wxc/src/treectrl.cpp:338: warning: `GetNextChild' is deprecated (declared at
These are "innocent" warnings -- wxHaskell still uses the deprecated interface.
It would be nice to upgrade though ..
g++ -c wxc/src/image.cpp -o
out/wxc/image.o -MD -IC:/cygwin/usr/local/include -IC:/cygwin/usr/local/lib/wx/include/msw-ansi-release-static-2.6 -IC:/
cygwin/usr/local/include/wx-2.6 -D__WIN95__ -D__WXMSW__ -Iwxc/include
wxc/src/image.cpp:124:2: warning: no newline at end of file
g++ -c wxc/src/apppath.cpp -o
out/wxc/apppath.o -MD -IC:/cygwin/usr/local/include -IC:/cygwin/usr/local/lib/wx/include/msw-ansi-release-static-2.6 -IC
:/cygwin/usr/local/include/wx-2.6 -D__WIN95__ -D__WXMSW__ -Iwxc/include
wxc/src/apppath.cpp:114:2: warning: no newline at end of file
g++ -c wxc/src/db.cpp -o
out/wxc/db.o -MD -IC:/cygwin/usr/local/include -IC:/cygwin/usr/local/lib/wx/include/msw-ansi-release-static-2.6 -IC:/cyg
win/usr/local/include/wx-2.6 -D__WIN95__ -D__WXMSW__ -Iwxc/include
wxc/src/db.cpp: In function `int wxDbColInf_GetColumnSize(wxDbColInf*)':
wxc/src/db.cpp:1035: `class wxDbColInf' has no member named `columnSize'
wxc/src/db.cpp: In function `int wxDbColInf_GetBufferLength(wxDbColInf*)':
wxc/src/db.cpp:1044: `class wxDbColInf' has no member named `bufferLength'
wxc/src/db.cpp: In function `wxDbColInf* wxDb_GetResultColumns(wxDb*, int*)':
wxc/src/db.cpp:1158: `class wxDbColInf' has no member named `columnSize'
make: *** [out/wxc/db.o] Error 1
Hmm, not good -- it is even my own code :-) An easy fix would be to disable the odbc
when building wxWidgets (./configure --disable-odbc).

However, I have build wxHaskell with odbc on Windows -- but I was using Visual C++ 6.0.
So, if you have visual studio, I recommend building it using the visual studio
project. It is all explained in the build guide. With wxHaskell, you would do:

> ./configure --with-msc  [--wxc-libname=wxcd]

open the visual studio project wxc/wxc-2.x.dsw
build the dll

> make

Anyways, I'll try to look into it -- it seems that the make commands for newer
wxWidgets is lagging behind (on Linux and MacOSX I normally build with odbc enabled).

-- Daan.

This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit
wxhaskell-users mailing list