<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.4: http://docutils.sourceforge.net/" />
-<title>Building wxPython 2.7 for Development and Testing</title>
+<meta name="generator" content="Docutils 0.4.1: http://docutils.sourceforge.net/" />
+<title>Building wxPython 2.8 for Development and Testing</title>
<link rel="stylesheet" href="default.css" type="text/css" />
</head>
<body>
-<div class="document" id="building-wxpython-2-7-for-development-and-testing">
-<h1 class="title">Building wxPython 2.7 for Development and Testing</h1>
+<div class="document" id="building-wxpython-2-8-for-development-and-testing">
+<h1 class="title">Building wxPython 2.8 for Development and Testing</h1>
<p>This file describes how I build wxWidgets and wxPython while doing
development and testing, and is meant to help other people that want
to do the same thing. I'll assume that you are using either a CVS
snapshot from <a class="reference" href="http://wxWidgets.org/snapshots/">http://wxWidgets.org/snapshots/</a>, a checkout from CVS, or
-one of the released wxPython-src-2.7.* tarballs. I'll also assume that
+one of the released wxPython-src-2.8.* tarballs. I'll also assume that
you know your way around your system, the compiler, etc. and most
importantly, that you know what you are doing! ;-)</p>
<p>If you want to also install the version of wxPython you build to be in
cd $WXDIR
mkdir bld
cd bld
-../configure --prefix=/opt/wx/2.7 \
+../configure --prefix=/opt/wx/2.8 \
--with-gtk \
--with-gnomeprint \
--with-opengl \
</pre>
<p>On OS X of course you'll want to use --with-mac instead of
--with-gtk and --with-gnomeprint.</p>
-<p>Notice that above I used a prefix option of "/opt/wx/2.7". You can
+<p>Notice that above I used a prefix option of "/opt/wx/2.8". You can
use whatever path you want, such as a path in your HOME dir or even
one of the standard prefix paths such as /usr or /usr/local if you
like, but using /opt this way lets me easily have multiple versions
and ports of wxWidgets "installed" and makes it easy to switch
between them, without impacting any versions of wxWidgets that may
have been installed via an RPM or whatever. For the rest of the
-steps below be sure to also substitute "/opt/wx/2.7" with whatever
+steps below be sure to also substitute "/opt/wx/2.8" with whatever
prefix you choose for your build.</p>
<p><strong>NOTE</strong>: Due to a recent change there is currently a dependency
problem in the multilib builds of wxWidgets on OSX, so I have
.make install
</pre>
<p>When it's done you should have an installed set of files under
-/opt/wx/2.7 containing just wxWidgets. Now to use this version of
-wxWidgets you just need to add /opt/wx/2.7/bin to the PATH and set
-LD_LIBRARY_PATH (or DYLD_LIBRARY_PATH on OS X) to /opt/wx/2.7/lib.</p>
+/opt/wx/2.8 containing just wxWidgets. Now to use this version of
+wxWidgets you just need to add /opt/wx/2.8/bin to the PATH and set
+LD_LIBRARY_PATH (or DYLD_LIBRARY_PATH on OS X) to /opt/wx/2.8/lib.</p>
</li>
<li><p class="first">I also have a script to help me build wxPython and it is checked in
to the CVS as wxWidgets/wxPython/b, but you probably don't want to
other version of it found first, then you can add this to the
command line to ensure your new one is used instead:</p>
<pre class="literal-block">
-WX_CONFIG=/opt/wx/2.7/bin/wx-config
+WX_CONFIG=/opt/wx/2.8/bin/wx-config
</pre>
<p>By default setup.py will assume that you built wxWidgets to use
GTK2. If you built wxWidgets to use GTK 1.2.x then you should add
PYTHONPATH to the wxPython dir located in the source tree. For
example:</p>
<pre class="literal-block">
-export LD_LIBRARY_PATH=/opt/wx/2.7/lib
+export LD_LIBRARY_PATH=/opt/wx/2.8/lib
export PYTHONPATH=$WXDIR/wxPython
cd $WXDIR/wxPython/demo
python2.5 demo.py
projects / wxWidgets.git / blobdiff