Updates to readmes, etc.

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_2_4_BRANCH@18306 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775

wxPython/BUILD.osx.txt

@@ -1,14 +1,8 @@
 Building wxPython on Mac OS X
 -----------------------------
 
-NOTE:  OS X support is EXPERIMENTAL at this time.  Most things 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.x
-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
 that you know your way around a command line and that you know how to
 get things from various CVS repositories as needed.

wxPython/BUILD.unix.txt

@@ -100,7 +100,7 @@ D. If using the sources (either from the tarball or from CVS) then
 	cd wxWindows   # or whatever your top-level directory is called
 	mkdir build
 	cd build
-	../configure --with-gtk
+	../configure --with-gtk --enable-geometry
 
    There are gobs and gobs of options for the configure script, run
    ../configure --help to see them all.  I'll describe some that I find
@@ -118,33 +118,6 @@ D. If using the sources (either from the tarball or from CVS) then
    special debugging code in wxWindows by defining the __WXDEBUG__
    macro.  You'll get some extra asserts, failure logging, etc.
 
-   To make a static library and not make a shared library, use the
-   --disable-shared and --enable-static flags.
-
-   NOTE: There is a potential type mismatch between Python and wxGTK.
-   This happens if Python defines some flags that turn on 64-bit file
-   offset support and wxGTK does not.  This causes some basic types,
-   like off_t, to be typedef'd differently causing the C++ method
-   signatures to be incompatible and giving link errors at runtime.
-   If you get errors upon running a wxPython script that looks
-   something like this:
-
-     SeekI_13wxInputStream10wxSeekMode: referenced symbol not found
-
-   then that is probably the issue.  This can be fixed in the current
-   code by predefining these flags before wxGTK's configure is run,
-   for example:
-
-     export CFLAGS="-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -DHAVE_LARGEFILE_SUPPORT"
-     export CXXFLAGS=$CFLAGS
-     ../configure --with-gtk --with-opengl --enable-debug
-
-   In the 2.3.3 final release there will be a real configure flag for
-   it, and it should be enabled by default.  You will be able to use
-   --enable-largefile or --disable-largefile to control it.  If you
-   still get this or a similar error with 2.3.3 then try disabling
-   largefile support in wxGTK.
-
 E. Now just compile and install.  You need to use GNU make, so if your
    system has something else get GNU make and build and install it and
    use it instead of your system's default make command.

wxPython/BUILD.win32.txt

@@ -105,8 +105,10 @@ D. Change to the wx2\include\wx\msw directory and copy setup0.h to
    the default setup0.h in my setup.h, but you can experiment with
    other settings if you like:
 
+
 	 WXWIN_COMPATIBILITY_2_2	0
          wxDIALOG_UNIT_COMPATIBILITY	0
+	 wxUSE_DEBUG_CONTEXT		1
 	 wxUSE_MEMORY_TRACING		1
          wxUSE_CMDLINE_PARSER		0
 	 wxUSE_FSVOLUME			0

wxPython/distrib/README.1st.txt

@@ -13,9 +13,10 @@ building your own copy of wxPython from the sources contained in this
 archive.  If you wish to use the released wxGTK binary as has been
 done in the past then you can still follow the old build directions in
 wxPython/BUILD.unix.txt.  If you are building for Windows or Mac OS X
-then you should look at BUILD.win32.txt or BUILD.osx.txt respectivly.
+then you should look at wxPython/BUILD.win32.txt or
-In all these cases you should use the IN_CVS_TREE=1 flag since this
+wxPython/BUILD.osx.txt respectivly.  In all these cases you should use
-archive is really just a modified CVS snapshot.
+the IN_CVS_TREE=1 flag since this archive is really just a modified
+CVS snapshot.
 
 If, on the other hand, you would like to build Linux/Unix binaries
 with a private copy of wxGTK like what I am now distributing then
@@ -42,16 +43,23 @@ Clear as mud?  Good.  Let's get started.
                      --prefix=$WXPREF \
                      --enable-rpath=$WXPREF/lib \
                      --with-opengl \
+		     --enable-geometry \
                      --enable-optimise \
                      --enable-debug_flag \
+
+   You may want to use --enable-debug instead of --enable-optimise if
+   you need to run though a debugger and want full debugging symbols.
+
+   if you want to use the image and zlib libraries included with
+   wxWindows instead of those already installed on your system, (for
+   example, to reduce dependencies on 3rd party libraries) then you
+   can add these flags to the configure command:
+
                      --with-libjpeg=builtin \
                      --with-libpng=builtin \
                      --with-libtiff=builtin \
                      --with-zlib=builtin
 
-   You may want to use --enable-debug instead of --enable-optimise if
-   you need to run though a debugger and want full debugging symbols.
-
 
 3. Build and install wxGTK.  (You may need to be root for the last
    step, depending on where your WXPREF is.)