This document will describe the few differences and additions to the content in the BUILD document for installing wxPython built from source. Please follow the intstructions both in this file and in BUILD to perform this task. Where there is overlap the items described here will take precedence for doing installations.
-When building wxWidgets you need to decide if you want it to be a private copy only accessed by wxPython, or if you would like it to @@ -49,7 +49,7 @@ find the wxWidgets shared libraries. You can hard code the library path into the binaries by using the rpath option when configuring wxWidgets. For example:
---enable-rpath=/opt/wx/2.6/lib \ +--enable-rpath=/opt/wx/2.8/lib \
SOLARIS NOTE: The --enable-rpath option may cause problems when using wxGTK on Solaris when compiling wxPython as described below. @@ -69,7 +69,7 @@ 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.5 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 @@ -81,8 +81,8 @@ contained in the PYTHONPATH environment variable.
Installing wxPython on OS X is nearly the same as the Unix instructions above, except for a few small, but important details:
Build wxWidgets and wxPython as described in BUILD.txt. If you would rather have a version without the code that turns runtime @@ -131,7 +131,7 @@ python setup.py install found at runtime by the extension modules without requiring that they be installed on the PATH:
-copy %WXWIN%\lib\vc_dll\wx*h_*.dll c:\Python23\Lib\site-packages\wx +copy %WXWIN%\\lib\\vc_dll\\wx*h_*.dll c:\\Python25\\Lib\\site-packages\\wx