suppress an assert when a combobox receives WM_KILLFOCUS while it is being destroyed

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

diff --git a/wxPython/BUILD.osx.txt b/wxPython/BUILD.osx.txt
index 198e1336fcffc9efb9d9a9d7f563c2fd46c81453..1af6b0d1890c1f6da029bcdc2fd1bb44cdf93df5 100644 (file)
--- a/wxPython/BUILD.osx.txt
+++ b/wxPython/BUILD.osx.txt
@@ -2,7 +2,11 @@ Building wxPython on Mac OS X
 -----------------------------
 
 NOTE:  OS X support is HIGHLY EXPERIMENTAL at this time.  Most things
 -----------------------------
 
 NOTE:  OS X support is HIGHLY EXPERIMENTAL at this time.  Most things

-       don't work correctly (or at all) yet.
+       are working now, but a few still don't.  I know about most of
+       them and am addressing them as I have time.  If you have any
+       ideas about a fix for the stuff that's still broken then
+       please persue them and send the fixes to me.
+

 
 These are the steps I have used for building wxPython on Mac OS X 10.1
 with the Apple Developer Tools, a.k.a the Darwin version.  I assume
 
 These are the steps I have used for building wxPython on Mac OS X 10.1
 with the Apple Developer Tools, a.k.a the Darwin version.  I assume


@@ -10,53 +14,71 @@ that you know your way around a command line and that you know how to
 get things from various CVS repositories as needed.
 
 
 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. Python 2.2 is required.  There is a disk image with an installer
+   package in the wxPython Sourceforge download area, in this group:
+
+   http://sourceforge.net/project/showfiles.php?group_id=10718&release_id=84730
+
+   If, for some reason you need to build your own Python, get the
+   source from www.python.org and follow theinstructions in the
+   Mac/OSX/README file to build and install Python.app and the
+   Python.framework.

 
 

-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:
+   If you build your own Python then 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:

 
         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
 
 
         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
 

-3. In a wxWindows CVS tree make a build directory.
+   Also, if you create a /usr/local/bin/pythonw script like the
+   following then you can run Python GUI apps (like wxPython) directly
+   from the command line:
+
+       #!/bin/sh
+       exec /Applications/Python.app/Contents/MacOS/python $@
+
+   Be sure to give this script execute permissions:
+
+       sudo chmod +x /usr/local/bin/pythonw
+
+   If you would like to make a MachoPython installer from what you
+   built then you may want to look at the scripts I use to do it
+   located in wxPython/distrib/mac/buildPython.
+
+   One last thing, make sure that /usr/local/bin is in your PATH
+   environment variable.
+
+
+2. In a wxWindows CVS tree make a build directory.

 
        cd ~/proj/wxWindows     # or wherever you put it
        mkdir build
 
 
        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
 
 
         cd build
        ../configure --with-mac --with-opengl --enable-debug
 

-5. Make and install wxMac.
+4. Make and install wxMac.

 
        make
        sudo make install
 
 
        make
        sudo make install
 

-6. Build wxPython for testing (without installing it.)
+5. Build and install wxPython.

 
        cd ../wxPython
 
        cd ../wxPython

-       python setup.py IN_CVS_TREE=1 build_ext --inplace --debug
+       python setup.py IN_CVS_TREE=1 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.
+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
 
        cd demo

-       ln -s ../wxPython .
-
-8. Now just navigate in the Finder to the demo directory and double
-   click demo.py, or simple.py, or whatever you want to run.
-   (Unfortunately it can't be done from the commandline in a terminal
-   window.  You can open the Console app to see any tracebacks or
-   other output.)
+       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
    the patches to me.  <wink>
 
 --Robin