Installing wxPython 2.5 from Source

Installing wxPython 2.8 from Source

This document will describe the few differences and additions to the -content in BUILD.txt for installing wxPython built from source. -Please follow the intstructions both in this file and in BUILD.txt to -perform this task. Where there is overlap the items described here -will take precedence.

Installing on Unix-like Systems (not OS X)

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

Installing on Unix-like Systems (not OS X)

When building wxWindows you need to decide if you want it to be a +
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 be installed in a stanard location such as /usr. Or perhaps you -already have a version of wxWindows installed on your system (such +already have a version of wxWidgets installed on your system (such as from an RPM) and you want wxPython to use that version too. If so then you'll want to ensure that the flags and options used to build the installed version are compatible with wxPython.
If you do decide to build and install your own wxWindows then there +
If you do decide to build and install your own wxWidgets then there are a few tweaks to the configure flags described in BUILD.txt that you will probably want to make. Instead of --enable-debug use this configure flag:
```
 --enable-optimize \
 
```
-
Normally I also use the following flag in order to have wxWindows +
Normally I also use the following flag in order to have wxWidgets runtime assertions turned into Python exceptions where possible. It does add extra code to the build but probably not enough to worry about it. However if you want to get as lean a build as possible you can leave it out, but if your code does something bad -then instead of exceptions you'll likely get a crash.
-
-
--enable-debug_flag
-
-
If you are building a private copy of wxWindows (IOW, not installed +then instead of exceptions you'll likely get a crash:
+
```
+--enable-debug_flag \
+
```
+
If you are building a private copy of wxWidgets (IOW, not installed in a standard library location) then it can be kind of a hassle to always have to set the LD_LIBRARY_PATH variable so wxPython can -find the wxWindows shared libraries. You can hard code the library +find the wxWidgets shared libraries. You can hard code the library path into the binaries by using the rpath option when configuring -wxWindows. For example:
+wxWidgets. For example:
```
---enable-rpath=/opt/wx/2.5/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. @@ -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.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 @@ -79,15 +81,15 @@ contained in the PYTHONPATH environment variable.

Installing on OS X

Installing wxPython on OS X is nearly the same as the Unix instructions above, except for a few small, but important details:

The --enable-rpath configure option is not needed since the path to -the wxWindows dylibs will automatically be encoded into the +the wxWidgets dylibs will automatically be encoded into the extension modules when they are built. If you end up moving the -wxWindows dynlibs to some other location (such as inside the .app +wxWidgets dynlibs to some other location (such as inside the .app bundle of your applicaiton for distribution to other users,) then you will need to set DYLD_LIBRARY_PATH to this location so the dylibs can be found at runtime.

Installing on Windows

Build wxWindows and wxPython as described in BUILD.txt. If you +
Build wxWidgets and wxPython as described in BUILD.txt. If you would rather have a version without the code that turns runtime assertions into Python exceptions, then use "release" instead of -"hybrid" when building wxWindows and add "FINAL=1" to the setup.py +"hybrid" when building wxWidgets and add "FINAL=1" to the setup.py command line.
Install wxPython like this:
+
Install wxPython like this. Remember to add any additional flags +you added for the build such as UNICODE or USE_SWIG:
```
 python setup.py install
 
```
Copy the wxWindows DLLs to the wx package directory so they can be +
Copy the wxWidgets DLLs to the wx package directory so they can be found at runtime by the extension modules without requiring that they be installed on the PATH:
```
-copy %WXWIN%\BIN\wx*h_*.dll c:\Python23\Lib\site-pacakges\wx
+copy %WXWIN%\\lib\\vc_dll\\wx*h_*.dll c:\\Python25\\Lib\\site-packages\\wx
 
```

- -