2004-02-04 18:39:15 -05:00
|
|
|
<?xml version="1.0" encoding="iso-8859-1" ?>
|
|
|
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
|
|
|
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
|
|
|
|
|
<head>
|
|
|
|
|
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
|
|
|
|
|
<meta name="generator" content="Docutils 0.3.1: http://docutils.sourceforge.net/" />
|
|
|
|
|
<title>Installing wxPython 2.5 from Source</title>
|
|
|
|
|
<link rel="stylesheet" href="default.css" type="text/css" />
|
|
|
|
|
</head>
|
|
|
|
|
<body>
|
|
|
|
|
<div class="document" id="installing-wxpython-2-5-from-source">
|
|
|
|
|
<h1 class="title">Installing wxPython 2.5 from Source</h1>
|
|
|
|
|
<p>This document will describe the few differences and additions to the
|
2004-04-01 13:03:45 -05:00
|
|
|
content in the <a class="reference" href="BUILD.html">BUILD</a> document for installing wxPython built from
|
|
|
|
|
source. Please follow the intstructions both in this file and in
|
|
|
|
|
<a class="reference" href="BUILD.html">BUILD</a> to perform this task. Where there is overlap the items
|
|
|
|
|
described here will take precedence for doing installations.</p>
|
2004-02-04 18:39:15 -05:00
|
|
|
<div class="section" id="installing-on-unix-like-systems-not-os-x">
|
|
|
|
|
<h1><a name="installing-on-unix-like-systems-not-os-x">Installing on Unix-like Systems (not OS X)</a></h1>
|
|
|
|
|
<ol class="arabic">
|
2004-03-12 15:02:39 -05:00
|
|
|
<li><p class="first">When building wxWidgets you need to decide if you want it to be a
|
2004-02-04 18:39:15 -05:00
|
|
|
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
|
2004-03-12 15:02:39 -05:00
|
|
|
already have a version of wxWidgets installed on your system (such
|
2004-02-04 18:39:15 -05:00
|
|
|
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.</p>
|
|
|
|
|
</li>
|
2004-03-12 15:02:39 -05:00
|
|
|
<li><p class="first">If you do decide to build and install your own wxWidgets then there
|
2004-02-04 18:39:15 -05:00
|
|
|
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:</p>
|
|
|
|
|
<pre class="literal-block">
|
|
|
|
|
--enable-optimize \
|
|
|
|
|
</pre>
|
2004-03-12 15:02:39 -05:00
|
|
|
<p>Normally I also use the following flag in order to have wxWidgets
|
2004-02-04 18:39:15 -05:00
|
|
|
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
|
2004-04-01 13:03:45 -05:00
|
|
|
then instead of exceptions you'll likely get a crash:</p>
|
|
|
|
|
<pre class="literal-block">
|
|
|
|
|
--enable-debug_flag \
|
|
|
|
|
</pre>
|
2004-03-12 15:02:39 -05:00
|
|
|
<p>If you are building a private copy of wxWidgets (IOW, not installed
|
2004-02-04 18:39:15 -05:00
|
|
|
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
|
2004-03-12 15:02:39 -05:00
|
|
|
find the wxWidgets shared libraries. You can hard code the library
|
2004-02-04 18:39:15 -05:00
|
|
|
path into the binaries by using the rpath option when configuring
|
2004-03-12 15:02:39 -05:00
|
|
|
wxWidgets. For example:</p>
|
2004-02-04 18:39:15 -05:00
|
|
|
<pre class="literal-block">
|
|
|
|
|
--enable-rpath=/opt/wx/2.5/lib \
|
|
|
|
|
</pre>
|
|
|
|
|
<p>SOLARIS NOTE: The --enable-rpath option may cause problems when
|
|
|
|
|
using wxGTK on Solaris when compiling wxPython as described below.
|
|
|
|
|
The woraround is to not use --enable-rpath flag for configure, but
|
|
|
|
|
in that case all wxPython applications <em>must</em> have the
|
|
|
|
|
LD_LIBRARY_PATH set to include $WXPREF/lib, or you can use the
|
|
|
|
|
'crle' program to modify the runtime linking environment. If this
|
|
|
|
|
is the only installation of wxGTK on the system then you can use a
|
|
|
|
|
system library path for prefix and not have to worry about it at
|
|
|
|
|
all.</p>
|
|
|
|
|
</li>
|
|
|
|
|
<li><p class="first">Build and install wxGTK as described in BUILD.txt.</p>
|
|
|
|
|
</li>
|
|
|
|
|
<li><p class="first">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
|
2004-10-22 11:21:38 -04:00
|
|
|
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:</p>
|
2004-02-04 18:39:15 -05:00
|
|
|
<pre class="literal-block">
|
2004-10-22 11:21:38 -04:00
|
|
|
python2.3 setup.py install
|
2004-02-04 18:39:15 -05:00
|
|
|
</pre>
|
|
|
|
|
<p>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
|
|
|
|
|
add "--root=<path>" after the "install" command. This will use
|
|
|
|
|
<path> as the prefix and will install scripts to a bin subdir and
|
|
|
|
|
the wxPython packages to a lib subdir. To use wxPython like this
|
|
|
|
|
you'll need to ensure that the directory containing wxPython is
|
|
|
|
|
contained in the PYTHONPATH environment variable.</p>
|
|
|
|
|
</li>
|
|
|
|
|
</ol>
|
|
|
|
|
</div>
|
|
|
|
|
<div class="section" id="installing-on-os-x">
|
|
|
|
|
<h1><a name="installing-on-os-x">Installing on OS X</a></h1>
|
|
|
|
|
<p>Installing wxPython on OS X is nearly the same as the Unix
|
|
|
|
|
instructions above, except for a few small, but important details:</p>
|
|
|
|
|
<ol class="arabic simple">
|
|
|
|
|
<li>The --enable-rpath configure option is not needed since the path to
|
2004-03-12 15:02:39 -05:00
|
|
|
the wxWidgets dylibs will automatically be encoded into the
|
2004-02-04 18:39:15 -05:00
|
|
|
extension modules when they are built. If you end up moving the
|
2004-03-12 15:02:39 -05:00
|
|
|
wxWidgets dynlibs to some other location (such as inside the .app
|
2004-02-04 18:39:15 -05:00
|
|
|
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.</li>
|
|
|
|
|
<li>Depending on the version of OS X Python may be installed in
|
|
|
|
|
different locations. On 10.2 (Jaguar) you need to download and
|
|
|
|
|
install MacPython-OSX-2.3 from <a class="reference" href="http://www.python.org/">http://www.python.org/</a> and the
|
|
|
|
|
Python Framework will then be installed in /Library/Frameworks. On
|
|
|
|
|
10.3 (Panther) Apple supplies the Python Framework as part of the
|
|
|
|
|
OS install, but it will be located in /System/Library/Frameworks
|
2004-06-09 01:40:10 -04:00
|
|
|
instead. However, on Panther the site-packages dir is sym-linked
|
|
|
|
|
to /Library/Python/2.3 so the wxPython packages will end up there,
|
2004-02-04 18:39:15 -05:00
|
|
|
although they will still be visible from site-packages. If you are
|
|
|
|
|
building distributions of wxPython to be installed on other
|
|
|
|
|
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...</li>
|
2004-10-22 11:21:38 -04:00
|
|
|
<li>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.</li>
|
2004-02-04 18:39:15 -05:00
|
|
|
</ol>
|
|
|
|
|
</div>
|
|
|
|
|
<div class="section" id="installing-on-windows">
|
|
|
|
|
<h1><a name="installing-on-windows">Installing on Windows</a></h1>
|
|
|
|
|
<ol class="arabic">
|
2004-03-12 15:02:39 -05:00
|
|
|
<li><p class="first">Build wxWidgets and wxPython as described in BUILD.txt. If you
|
2004-02-04 18:39:15 -05:00
|
|
|
would rather have a version without the code that turns runtime
|
|
|
|
|
assertions into Python exceptions, then use "release" instead of
|
2004-03-12 15:02:39 -05:00
|
|
|
"hybrid" when building wxWidgets and add "FINAL=1" to the setup.py
|
2004-02-04 18:39:15 -05:00
|
|
|
command line.</p>
|
|
|
|
|
</li>
|
2004-06-09 01:40:10 -04:00
|
|
|
<li><p class="first">Install wxPython like this. Remember to add any additional flags
|
|
|
|
|
you added for the build such as UNICODE or USE_SWIG:</p>
|
2004-02-04 18:39:15 -05:00
|
|
|
<pre class="literal-block">
|
|
|
|
|
python setup.py install
|
|
|
|
|
</pre>
|
|
|
|
|
</li>
|
2004-03-12 15:02:39 -05:00
|
|
|
<li><p class="first">Copy the wxWidgets DLLs to the wx package directory so they can be
|
2004-02-04 18:39:15 -05:00
|
|
|
found at runtime by the extension modules without requiring that
|
|
|
|
|
they be installed on the PATH:</p>
|
|
|
|
|
<pre class="literal-block">
|
2004-06-09 01:40:10 -04:00
|
|
|
copy %WXWIN%\lib\vc_dll\wx*h_*.dll c:\Python23\Lib\site-packages\wx
|
2004-02-04 18:39:15 -05:00
|
|
|
</pre>
|
|
|
|
|
</li>
|
|
|
|
|
</ol>
|
|
|
|
|
</div>
|
|
|
|
|
</div>
|
|
|
|
|
</body>
|
|
|
|
|
</html>
|
