1 wxCocoa is still a work in progress.
3 To compile it, you will need Apple's Developer Tools. However, please
4 note that any work to make it suitable for GNUstep (which will require
5 a GCC release with Objective-C++) will be much appreciated.
7 For the time being, the standard configure/make method works. You will
8 want to build static because there are a number of unimplemented functions
9 that a shared library will need (becuase of wxWidgets code internally using
10 them) but that a static library will not (because most of the samples
13 On my system I have the following:
15 Checked out CVS source is in:
16 /Users/dfe/devel/wxHEADcommit/wxWidgets
17 Debug build directory is:
18 /Users/dfe/devel/wxHEADcommit/BUILD_COCOAd
20 From the debug build directory:
21 $ ../wxWidgets/configure --with-cocoa --enable-debug --disable-shared
27 You may also need to configure the library --without-expat. It didn't
28 build last time I checked, but then again, several improvements have
31 For other samples, you will need to provide at the very least an empty
32 resource fork so the OS will recognize it as a GUI application.
34 From the debug build directory:
37 $ true | /Developer/Tools/Rez -t APPL -o drawing
40 Note that the empty resource fork doesn't actually allow the app to be
41 started from the Finder (it thinks it's a classic app!) but does allow
42 it to run with a menubar and proper event handling from the command line.
44 I suspect (but am uncertain) that if we provided an empty plist resource
45 that the app would be recognized as a proper OS X application. Obviously,
46 bundles would be preferrable, and any work on Bakefile (see
47 http://bakefile.sf.net/) would be much appreciated. wxMac also needs
48 bundle building restored since the switch to Bakefile.