wxCheckListBox doesn't require wxUSE_OWNER_DRAWN when using WXUNIVERSAL

[wxWidgets.git] / wxPython / docs / INSTALL.txt

diff --git a/wxPython/docs/INSTALL.txt b/wxPython/docs/INSTALL.txt
index 702977969485ef4d1934ee1e7f41312b34785f5e..848359181f2d9d3cd0091eeb4d26c49153f12cae 100644 (file)
--- a/wxPython/docs/INSTALL.txt
+++ b/wxPython/docs/INSTALL.txt
@@ -1,4 +1,4 @@
-Installing wxPython 2.5 from Source
+Installing wxPython 2.6 from Source
 ===================================
 
 
@@ -48,7 +48,7 @@ Installing on Unix-like Systems (not OS X)
    path into the binaries by using the rpath option when configuring
    wxWidgets.  For example::
 
-                     --enable-rpath=/opt/wx/2.5/lib \
+                     --enable-rpath=/opt/wx/2.6/lib \
 
    SOLARIS NOTE: The --enable-rpath option may cause problems when
    using wxGTK on Solaris when compiling wxPython as described below.
@@ -66,9 +66,11 @@ Installing on Unix-like Systems (not OS X)
 
 4. In addition to building wxPython as described in BUILD.txt, you can
    install it to Python's site-packages dir, as well as some scripts
-   into the same bin dir used by Python by using this command::
+   into the same bin dir used by Python by using this command, plus
+   whatever WXPORT, UNICODE, etc. settings you used for the initial
+   build step::
 
-       python2.3 setup.py install
+       python2.3 setup.py install 
 
    If you would like to install to some place besides the prefix where
    Python is installed, (such as to your home directory) then you can
@@ -110,9 +112,9 @@ instructions above, except for a few small, but important details:
    you do yourself will end up in /Library/Frameworks even on
    Panther...
 
-3. You need to use pythonw at the command line or PythonLauncher app
-   to run wxPython apps, otherwise the app will not be able to fully
-   use the GUI display.
+3. You need to use pythonw at the command line or the PythonLauncher
+   app to run wxPython apps, otherwise the app will not be able to
+   fully use the GUI display.