1 Installing on MacOS X

Check your path to make sure you are using your wxWidgets and not the default Mac one

cabal install wx

2 Known working configurations

Date

Arch

OS/XCode

wxWidgets

wxHaskell

GHC

Haskell Platform

2012-04

Intel 64-bit

Lion (10.7.3), Xcode 4.3

2.9.3 (HomeBrew)

0.90

7.0.4

2011.3.0.0

3 Using wxHaskell on MacOS X platforms

Even though graphical applications on MacOS X look great, it is a still a developers nightmare to get them working :-). Furthermore, the MacOS X port of wxWidgets is the least mature and still has some quirks. This page describes how to circumvent some of the pitfalls.

Graphical applications generated with GHC do not work if executed directly ‚Äì they need to be upgraded into MacOS X applications. The macosx-app script does this for you. It is provided with binary releases and resides in the bin directory of a source release. Creating a program now consists of the following steps:

Due to complicated MacOS X restrictions, graphical wxHaskell applications do not work directly when used from GHCi. Fortunately, Wolfgang Thaller has kindly provided an ingenious Haskell module that solves this problem. Just import the (compiled) module EnableGUI in your program and issue the following command to run main from your GHCi prompt:

The dynamic link libraries used by wxHaskell can not always be found. If your application seems to start (the icon bounces) but terminates mysteriously, you need to set the dynamic link library search path to the wxHaskell library directory. For example:

4 Troubleshooting

2009-04-01: we don't know for sure yet. macosx-app is just a shell script that runs Rez and also creates an application bundle. If you are a MacOS developer, especially a wxWidgets one, we would love some help answering this question.