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 @@ -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.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. @@ -65,9 +65,11 @@ all.
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 @@ -105,9 +107,9 @@ machines be careful to install to /Library/Python/2.3. To complicate things further, the Jaguar version, or a custom build you do yourself will end up in /Library/Frameworks even on Panther...