(→WxHaskell Windows issue.)
m (→WxHaskell Windows issue.)
Latest revision as of 12:58, 11 February 2011
 1 Corrections needed?
The section titled Building Haskell says that on Windows the WXCFG environment variable should be set to "gcc_dll/mswu". Later in the same section, the example given sets it to "gcc_dll\mswu". When following through these instructions I needed to set mine to "gcc_dll\mswud". --Mikesteele81 14:20, 8 July 2010 (UTC)
Okay. Now I followed what I thought was the same procedure on another computer, and this time it really did get placed in the gcc_dll\mswu folder. --Mikesteele81 19:00, 10 July 2010 (UTC)
 2 WxHaskell Windows issue.
I followed the instructions and could not get WxHaskell to work via "cabal install wx". After some discussion in #haskell, I finally managed to get it to work under Windows Vista with Haskell Platform 2010.2.0.0, which includes GHC 6.12.3.
The problem was that MingW32 used GCC 3.*, which simply could not compile wxWidgets 2.8.11. Instead I used MingW 4.4.0, http://code.google.com/p/qp-gcc/, and proceeded to follow the rest of the instructions and everything worked out.
I would like the following link, http://haskell.org/haskellwiki/WxHaskell/Building, to reflect my experience as a Windows user.
Where it says, "MinGW 5.1.6 can be downloaded from MinGW", also mention that if the first step doesn't work, then download MingW from, http://code.google.com/p/qp-gcc/, and get the "all" version.
An issue I have noticed, is that after installing Haskell Platform 2010.2.0.0, i noticed that there are no cabal or cabal-install command line tools. Its a nitpick, but it makes building and installing wxhaskell pretty tedious.