]> git.saurik.com Git - wxWidgets.git/blame - wxPython/BUILD.osx.txt
Added build instructions for OS X.
[wxWidgets.git] / wxPython / BUILD.osx.txt
CommitLineData
b6e5c445
RD
1Building wxPython on Mac OS X
2-----------------------------
3
4NOTE: OS X support is HIGHLY EXPERIMENTAL at this time. Most things
5 don't work correctly (or at all) yet.
6
7These are the steps I have used for building wxPython on Mac OS X 10.1
8with the Apple Developer Tools, a.k.a the Darwin version. I assume
9that you know your way around a command line and that you know how to
10get things from various CVS repositories as needed.
11
12
131. As of this writing the CVS version of Python (2.2b1+) is required.
14 You can get it via anonymous CVS from the Python project at
15 Sourceforge. Build Python.app and install it as described in the
16 Mac/OSX/README file in the Python distribution.
17
182. You may want to make a symlink or two in /usr/local/bin so that
19 this version of Python can be found from the command line. For
20 example:
21
22 cd /usr/local/bin
23 sudo ln -s /Library/Frameworks/Python.framework/Versions/2.2/bin/python2.2.exe python2.2
24 sudo ln -s python2.2 python
25
263. In a wxWindows CVS tree make a build directory.
27
28 cd ~/proj/wxWindows # or wherever you put it
29 mkdir build
30
314. Run configure from that build directory.
32
33 cd build
34 ../configure --with-mac --with-opengl --enable-debug
35
365. Make and install wxMac.
37
38 make
39 sudo make install
40
416. Build wxPython for testing (without installing it.)
42
43 cd ../wxPython
44 python setup.py IN_CVS_TREE=1 build_ext --inplace --debug
45
467. Test. The easiest way to do this from the CVS tree (witout having
47 to reinstall after every build) is to make a symlink in the demo
48 directory to the wxPython package dir, and then run stuff directly
49 from the demo.
50
51 cd demo
52 ln -s ../wxPython .
53
548. Now just navigate in the Finder to the demo directory and double
55 click demo.py, or simple.py, or whatever you want to run.
56 (Unfortunately it can't be done from the commandline in a terminal
57 window. You can open the Console app to see any tracebacks or
58 other output.)
59
609. Figure out what's wrong, figure out how to fix it, and then send
61 the patches to me. <wink>
62
63--Robin
64
65
66
67
68
69