Ensure you have a recent GHC compiler – version 6.10.3 or higher is recommended. In principle, any Haskell 98 compiler that supports the standard FFI libraries along with cabal install should work, but we typically test new releases only against the latest version of Haskell Platform for the supported targets. We have discontinued support for building without cabal.
- Windows: You will need wx-config for Windows, MinGW 5.1.6 and MSYS 0.1.11 (these are the latest versions at the time of writing). You must select the C++ compiler option when installing MinGW.
- Mac OS X: you need to install the gcc compiler, which is part of the Apple Developer Tools. These tools are shipped with Panther and are installed by invoking Applications/Installers/Developer Tools/Developer.mdmg.
You should install the current stable version of wxWidgets for your platform - versions older than 2.8.1 are no longer supported. Build instructions are given for Windows - on most other platforms you should be able to obtain wxWidgets using your package manager (you may need -developer packages).
We assume in this guide that the variable $wxwin points to your wxWidgets installation directory, for example: ~/dev/wxGTK-2.8.10.
2 Getting wxWidgets
wxHaskell 0.13.x supports wxWidgets > 2.8.0 and < 2.9.0
- You can use the wxPack prebuilt binaries (the MinGW ones). This is a highly recommended approach.
- Alternatively, you can build using the MinGW compiler - instructions below.
- Mac OS X
- Tiger - do not use the wxMac 2.5 that comes pre-installed.
- Leopard - wxHaskell now supports wxWidgets 2.8.
- Lion - You will need to use wxWidgets 2.9.x and wxHaskell 0.90, as wxWidgets 2.8.x is not 64bit clean.
- Linux - the wxWidgets that ships with your system should work - wxWidgets 2.8 has been the default on most systems for quite some time now.
- wxGTK - wxHaskell supports wxGTK, and not wxX11. For any modern Unix system you almost certainly want wxGTK anyway.
- Installation on Ubuntu
- sudo apt-get install wx2.8-headers libwxgtk2.8-dev
See the wxWidgets site for more details.
3 Building wxWidgets (usually optional)
3.1 On Windows
Note: Microsoft compilers are no longer supported. The cabal build system cannot understand the output of wx-config for Microsoft compilers.
Note: The Haskell Platform 2010.1.0.0 installer shipped without C++ support. If you want to build wxHaskell on Windows using this Haskell Platform, please see 
Using the MSYS shell, and making sure that you have the C++ compiler option installed for MinGW as it is 'not' the default:
> cd /c/path/to/wxWidgets-2.8.10/build/msw > mingw32-make -f makefile.gcc BUILD=release SHARED=1 UNICODE=1
This will take quite some time and generate lots of text in the MSYS shell. Assuming it is successful, a DLL is generated in /c/path/to/wxWidgets/gcc_dll, which you will need to copy to a location where it can be found when running your executables.
3.2 On Unix systems
You should follow the instructions on the wxWidgets website if there are no suitable packages for your environment. You should use GCC to build wxWidgets, as this makes it more likely that cabal will understand the output of wx-config.
On most Unix platforms, wxWidgets build goes something like: create a mybuild directory in the wxWidgets directory, and run configure and make from that directory (and take the time to get some coffee :-).
> cd $wxwin > mkdir mybuild > cd mybuild > ../configure --enable-unicode > make > make install > cd ../contrib/src > make > make install
3.3 Testing wxWidgets build
Now try out a few samples of wxWidgets to see if it all works correctly:
> cd ../../samples/controls > make > ./controls
Note that you build from the local samples directory that resides in the mybuild directory.
And also try if wx-config works too:
> wx-config -v
ChengWei: I've found that if you put wx-config in some system directories, such as c:\windows\system32, 'cabal install wx' will complain "wx-config: does not exist". To put it in another directory in %PATH% will solve this problem. Tested on Windows 7, Haskell platform 2010 184.108.40.206.
4 Detailed Guide to Getting Going with wxPack on Windows
4.1 Installing on Windows
Follow SkyTreeBird's guide. It which walks you through the basic steps
- setting up environment variables
cabal install wx
Note that the best way to refer to WxWidgets in your PATH is probably to use the WXWIN variable that you set, eg.
The guide has been tested with the following configurations. Others may work too:
4.2 Troubleshooting Windows installation with cabal
These remarks refer to wx-0.13.2 and Haskell Platform 2011.4.0.0 on Windows 7.
Cabal package wx depends on wxcore which depends on wxdirect. By default cabal installs on a per user base, thus wxdirect.exe will be installed to
c:\Users\<YOUR NAME>\AppData\Roaming\cabal\bin\. This folder must be in your
cabal install wxcore to succeed.
Package wxcore-0.13.2 does not work well with wx-config revision 21 2006-10-19 (downloaded from here on Feb 2nd 2012). If
cabal install wxcore fails with an output containing "Usage: wx-config [options]" try this:
cabal unpack wxcore
Setup.hsand comment out/remove the line containing
runhaskell.exe Setup.hs configure --user
runhaskell.exe Setup.hs build
runhaskell.exe Setup.hs install
cabal install wx.