]>
Commit | Line | Data |
---|---|---|
1 | ---------------------------------------------------------------------------- | |
2 | NB: This is the old wxCocoa port, you almost certainly want to read | |
3 | docs/osx/install.txt for instructions about building wxOSX/Cocoa instead. | |
4 | ---------------------------------------------------------------------------- | |
5 | ||
6 | wxCocoa is still a work in progress. | |
7 | ||
8 | To compile it, you will need Apple's Developer Tools. However, please | |
9 | note that any work to make it suitable for GNUstep (which will require | |
10 | a GCC release with Objective-C++) will be much appreciated. | |
11 | ||
12 | Like most UNIX ports, the standard configure/make method works. You should | |
13 | be able to build the library as static or shared. I usually build static. | |
14 | ||
15 | On my system I have the following: | |
16 | ||
17 | Checked out CVS source is in: | |
18 | /Users/dfe/devel/wxHEADcommit/wxWidgets | |
19 | Debug build directory is: | |
20 | /Users/dfe/devel/wxHEADcommit/BUILD_COCOAd | |
21 | ||
22 | From the debug build directory: | |
23 | $ ../wxWidgets/configure --with-cocoa --enable-debug --disable-shared | |
24 | $ make | |
25 | $ cd samples/minimal | |
26 | $ make | |
27 | $ ./minimal.app/Contents/MacOS/minimal | |
28 | ||
29 | Like wxMac applications, wxCocoa applications are "bundled". For development | |
30 | purposes all this means is that an executable named "foo" needs to be | |
31 | inside a "foo.app/Contents/MacOS" directory. For deployment you will need | |
32 | an appropriate Info.plist and PkgInfo inside the foo.app/Contents directory. | |
33 | ||
34 | wxCocoa (and Cocoa in general) has no need for Mac OS resources. It | |
35 | certainly has no need for resource forks as no Mach-O applications should | |
36 | _ever_ have resource forks (note: Bakefile violates this right now). | |
37 | Please see the wxWiki and/or discuss this with wx-users before shipping | |
38 | any wxCocoa apps if you are new to the OS X platform. |