]>
Commit | Line | Data |
---|---|---|
b6e5c445 RD |
1 | Building wxPython on Mac OS X |
2 | ----------------------------- | |
3 | ||
4 | NOTE: OS X support is HIGHLY EXPERIMENTAL at this time. Most things | |
5 | don't work correctly (or at all) yet. | |
6 | ||
7 | These are the steps I have used for building wxPython on Mac OS X 10.1 | |
8 | with the Apple Developer Tools, a.k.a the Darwin version. I assume | |
9 | that you know your way around a command line and that you know how to | |
10 | get things from various CVS repositories as needed. | |
11 | ||
12 | ||
5ff5710d RD |
13 | 1. Python 2.2 is required. Get the source from www.python.org and |
14 | build Python.app and install it as described in the Mac/OSX/README | |
15 | file. | |
b6e5c445 RD |
16 | |
17 | 2. You may want to make a symlink or two in /usr/local/bin so that | |
18 | this version of Python can be found from the command line. For | |
19 | example: | |
20 | ||
21 | cd /usr/local/bin | |
5ff5710d | 22 | sudo ln -s /Library/Frameworks/Python.framework/Versions/2.2/bin/python2.2 python2.2 |
b6e5c445 RD |
23 | sudo ln -s python2.2 python |
24 | ||
25 | 3. In a wxWindows CVS tree make a build directory. | |
26 | ||
27 | cd ~/proj/wxWindows # or wherever you put it | |
28 | mkdir build | |
29 | ||
30 | 4. Run configure from that build directory. | |
31 | ||
32 | cd build | |
33 | ../configure --with-mac --with-opengl --enable-debug | |
34 | ||
35 | 5. Make and install wxMac. | |
36 | ||
37 | make | |
38 | sudo make install | |
39 | ||
40 | 6. Build wxPython for testing (without installing it.) | |
41 | ||
42 | cd ../wxPython | |
43 | python setup.py IN_CVS_TREE=1 build_ext --inplace --debug | |
44 | ||
45 | 7. Test. The easiest way to do this from the CVS tree (witout having | |
46 | to reinstall after every build) is to make a symlink in the demo | |
47 | directory to the wxPython package dir, and then run stuff directly | |
48 | from the demo. | |
49 | ||
50 | cd demo | |
51 | ln -s ../wxPython . | |
52 | ||
53 | 8. Now just navigate in the Finder to the demo directory and double | |
f54a35fe RD |
54 | click demo.py, or simple.py, or whatever you want to run. Or from |
55 | a command line you can run it this way: | |
56 | ||
57 | open -a Python demo.py | |
b6e5c445 RD |
58 | |
59 | 9. Figure out what's wrong, figure out how to fix it, and then send | |
60 | the patches to me. <wink> | |
61 | ||
62 | --Robin | |
63 | ||
64 | ||
65 | ||
66 | ||
67 | ||
68 |