Building wxPython on Mac OS X ----------------------------- These are the steps I have used for building wxPython on Mac OS X 10.x with the Apple Developer Tools, a.k.a the Darwin version. I assume that you know your way around a command line and that you know how to get things from various CVS repositories as needed. 1. "MacPython-OSX" 2.3 is required. If you don't have it already there is a disk image with an installer package at http://homepages.cwi.nl/~jack/macpython/download.html If, for some reason you need to build your own Python, get the source from www.python.org and follow the instructions in the Mac/OSX/README file to build and install the Python.framework and Python tools. One last thing, make sure that /usr/local/bin is in your PATH environment variable since that is where the new python and pythonw commands will be located. 2. In a wxWindows CVS tree make a build directory. (You can also use a CVS snapshot located in http://wxwindows.org/snapshots/ or the released wxPythonSrc-*.tr.gz archive.) cd ~/proj/wxWindows # or wherever you put it mkdir build 3. Run configure from that build directory. cd build ../configure --with-mac --with-opengl \ --enable-geometry \ --enable-optimise \ --with-libjpeg=builtin \ --with-libpng=builtin \ --with-libtiff=builtin \ If you want to add code that activates various runtime checks and assertion exceptions then add --enable-debug_flag. 4. Make and install wxMac. make sudo make install 5. Build and install wxPython. cd ../wxPython python setup.py build install If you would like to install to someplace besides the Python site-packages directory (such as to your home directory) then you can add "--root=" after the "install" command. To use wxPython like this you'll need to ensure that the directory containing wxPyrthon is contained in in the PYTHONPATH environment variable. 6. Test. Just navigate in the Finder to the demo directory and double click demo.py, or simple.py, or whatever you want to run. Or from a command line you can run it this way: cd demo pythonw demo.py 7. Figure out what's wrong, figure out how to fix it, and then send the patches to me. --Robin