2.7 --> 2.8

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@43424 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Robin Dunn
2006-11-14 21:52:48 +00:00
parent d5aea13b42
commit 13b955a755
2 changed files with 12 additions and 12 deletions

View File

@@ -1,11 +1,11 @@
Building wxPython 2.7 for Development and Testing
Building wxPython 2.8 for Development and Testing
=================================================
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 http://wxWidgets.org/snapshots/, 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! ;-)
@@ -74,7 +74,7 @@ place, then do the same for wxPython.
cd $WXDIR
mkdir bld
cd bld
../configure --prefix=/opt/wx/2.7 \
../configure --prefix=/opt/wx/2.8 \
--with-gtk \
--with-gnomeprint \
--with-opengl \
@@ -90,14 +90,14 @@ place, then do the same for wxPython.
On OS X of course you'll want to use --with-mac instead of
--with-gtk and --with-gnomeprint.
Notice that above I used a prefix option of "/opt/wx/2.7". You can
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.
**NOTE**: Due to a recent change there is currently a dependency
@@ -155,9 +155,9 @@ place, then do the same for wxPython.
.make install
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.
/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.
3. I also have a script to help me build wxPython and it is checked in
@@ -190,7 +190,7 @@ place, then do the same for wxPython.
other version of it found first, then you can add this to the
command line to ensure your new one is used instead::
WX_CONFIG=/opt/wx/2.7/bin/wx-config
WX_CONFIG=/opt/wx/2.8/bin/wx-config
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
@@ -224,7 +224,7 @@ place, then do the same for wxPython.
PYTHONPATH to the wxPython dir located in the source tree. For
example::
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

View File

@@ -1,4 +1,4 @@
Installing wxPython 2.7 from Source
Installing wxPython 2.8 from Source
===================================
@@ -48,7 +48,7 @@ Installing on Unix-like Systems (not OS X)
path into the binaries by using the rpath option when configuring
wxWidgets. For example::
--enable-rpath=/opt/wx/2.7/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.