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