Since wxGTK's wxGauge doesn't derive from wxGaugeBase it needs to have

[wxWidgets.git] / wxPython / BUILD.osx.txt

diff --git a/wxPython/BUILD.osx.txt b/wxPython/BUILD.osx.txt
index 159df03fb19e031f026f9d6c98177185491630f3..14bee6102da367693884b51030b2263cccba23d9 100644 (file)
--- a/wxPython/BUILD.osx.txt
+++ b/wxPython/BUILD.osx.txt
@@ -1,62 +1,66 @@
 Building wxPython on Mac OS X
 -----------------------------
 
-NOTE:  OS X support is HIGHLY EXPERIMENTAL at this time.  Most things
-       don't work correctly (or at all) yet.
 
-These are the steps I have used for building wxPython on Mac OS X 10.1
+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. Python 2.2 is required.  Get the source from www.python.org and
-   build Python.app and install it as described in the Mac/OSX/README
-   file.
+1. "MacPython-OSX" 2.3 is required.  There is a disk image with an
+   installer package in the wxPython Sourceforge download area, in
+   this group:
 
-2. You may want to make a symlink or two in /usr/local/bin so that
-   this version of Python can be found from the command line.  For
-   example:
+   http://sourceforge.net/project/showfiles.php?group_id=10718&release_id=84730
 
-        cd /usr/local/bin
-       sudo ln -s /Library/Frameworks/Python.framework/Versions/2.2/bin/python2.2 python2.2
-        sudo ln -s python2.2 python
+   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.
 
-3. In a wxWindows CVS tree make a build directory.
+   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
 
-4. Run configure from that build directory.
+3. Run configure from that build directory.
 
         cd build
        ../configure --with-mac --with-opengl --enable-debug
 
-5. Make and install wxMac.
+4. Make and install wxMac.
 
        make
        sudo make install
 
-6. Build wxPython for testing (without installing it.)
+5. Build and install wxPython.
 
        cd ../wxPython
-       python setup.py IN_CVS_TREE=1 build_ext --inplace --debug
+       python setup.py build install
 
-7. Test.  The easiest way to do this from the CVS tree (witout having
-   to reinstall after every build) is to make a symlink in the demo
-   directory to the wxPython package dir, and then run stuff directly
-   from the demo.
+   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=<path>" 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.
 
-       cd demo
-       ln -s ../wxPython .
-
-8. Now just navigate in the Finder to the demo directory and double
+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:
 
-        open -a Python demo.py
+       cd demo
+       pythonw demo.py
 
-9. Figure out what's wrong, figure out how to fix it, and then send
+7. Figure out what's wrong, figure out how to fix it, and then send
    the patches to me.  <wink>
 
 --Robin