Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Build and Install steps updated

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@26559 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Robin Dunn
2004-04-01 18:03:45 +00:00
parent 45cf74cccf
commit 2e957aaeb1
4 changed files with 122 additions and 87 deletions
Download Patch File Download Diff File Expand all files Collapse all files

89
wxPython/docs/BUILD.html
View File

@@ -20,11 +20,11 @@ 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 <p>If you want to also install the version of wxPython you build to be in
your site-packages dir and be your default version of wxPython, then a your site-packages dir and be your default version of wxPython, then a
few additional steps are needed, and you may want to use slightly few additional steps are needed, and you may want to use slightly
different options. See INSTALL.txt for more details. If you only use different options. See the <a class="reference" href="INSTALL.html">INSTALL</a> document for more details. If
the instructions in this BUILD.txt file then you will end up with a you only use the instructions in this <a class="reference" href="BUILD.html">BUILD</a> document file then you
separate installation of wxPython and you can switch back and forth will end up with a separate installation of wxPython and you can
between this and the release version that you may already have switch back and forth between this and the release version that you
installed.</p> may already have installed.</p>
<p>If you want to make changes to any of the <tt class="literal"><span class="pre">*.i</span></tt> files, (SWIG interface <p>If you want to make changes to any of the <tt class="literal"><span class="pre">*.i</span></tt> files, (SWIG interface
definition files,) or to regenerate the extension sources or renamer definition files,) or to regenerate the extension sources or renamer
modules, then you will need an up to date version of SWIG. Either get modules, then you will need an up to date version of SWIG. Either get
@@ -37,6 +37,13 @@ with an existing SWIG install for example) then you can set a setup.py
command-line variable named SWIG to be the full path name of the command-line variable named SWIG to be the full path name of the
executable and the wxPython build will use it. See below for an executable and the wxPython build will use it. See below for an
example.</p> example.</p>
<p>In the text below I'll use WXDIR with environment variable syntax
(either $WXDIR or %WXDIR%) to refer to the top level directory were
your wxWidgerts and wxPython sources are located. It will equate to
whereever you checked out the wxWidgets module from CVS, or untarred
the wxPythonSrc tarball to. You can either substitute the $WXDIR text
below with your actual dir, or set the value in the environment and
use it just like you see it below.</p>
<div class="section" id="building-on-unix-like-systems-e-g-linux-and-os-x"> <div class="section" id="building-on-unix-like-systems-e-g-linux-and-os-x">
<h1><a name="building-on-unix-like-systems-e-g-linux-and-os-x">Building on Unix-like Systems (e.g. Linux and OS X)</a></h1> <h1><a name="building-on-unix-like-systems-e-g-linux-and-os-x">Building on Unix-like Systems (e.g. Linux and OS X)</a></h1>
<p>These platforms are built almost the same way while in development <p>These platforms are built almost the same way while in development
@@ -52,6 +59,7 @@ build dir so I can easily blow away everything in the build dir and
rerun the script without having to remember the options I used rerun the script without having to remember the options I used
before:</p> before:</p>
<pre class="literal-block"> <pre class="literal-block">
cd $WXDIR
mkdir bld mkdir bld
cd bld cd bld
../configure --prefix=/opt/wx/2.5 \ ../configure --prefix=/opt/wx/2.5 \
@@ -114,10 +122,11 @@ wxWidgets you just need to add /opt/wx/2.5/bin to the PATH and set
LD_LIBRARY_PATH (or DYLD_LIBRARY_PATH on OS X) to /opt/wx/2.5/lib.</p> LD_LIBRARY_PATH (or DYLD_LIBRARY_PATH on OS X) to /opt/wx/2.5/lib.</p>
</li> </li>
<li><p class="first">I also have a script to help me build wxPython and it is checked in <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 probably don't want to use to the CVS as wxWidgets/wxPython/b, but you probably don't want to
it as it's very cryptic and expects that you want to run SWIG, so use it as it's very cryptic and expects that you want to run SWIG,
if you don't have the latest patched up version of SWIG then you'll so if you don't have the latest patched up version of SWIG then
probably get stuck. So I'll just give the raw commands instead.</p> you'll probably get stuck. So I'll just give the raw commands
instead.</p>
<p>We're not going to install the development version of wxPython with <p>We're not going to install the development version of wxPython with
these commands, so it won't impact your already installed version these commands, so it won't impact your already installed version
of the latest release. You'll be able test with this version when of the latest release. You'll be able test with this version when
@@ -129,10 +138,10 @@ sure to use the version of Python that you want to use when running
wxPython programs to run the setup.py commands below. I'll be wxPython programs to run the setup.py commands below. I'll be
using python2.3.</p> using python2.3.</p>
<p>Make sure that the first wx-config found on the PATH is the one you <p>Make sure that the first wx-config found on the PATH is the one you
installed above, and then change to the wxWidgets/wxPython dir and installed above, and then change to the $WXDIR/wxPython dir and
run the this command:</p> run the this command:</p>
<pre class="literal-block"> <pre class="literal-block">
cd wxPython cd $WXDIR/wxPython
python2.3 setup.py build_ext --inplace --debug python2.3 setup.py build_ext --inplace --debug
</pre> </pre>
<p>If your new wx-config script is not on the PATH, or there is some <p>If your new wx-config script is not on the PATH, or there is some
@@ -157,23 +166,24 @@ or something like that then you can add BUILD_GLCANVAS=0 to the
setup.py command line to disable the building of the glcanvas setup.py command line to disable the building of the glcanvas
module.</p> module.</p>
<p>When the setup.py command is done you should have fully populated <p>When the setup.py command is done you should have fully populated
wxPython and wx packages locally in wxWidgets/wxPython/wxPython and wxPython and wx packages locally in $WXDIR/wxPython/wxPython and
.../wx, with all the extension modules (<tt class="literal"><span class="pre">*.so</span></tt> files) located in the $WXDIR/wxPython/wx, with all the extension modules (<tt class="literal"><span class="pre">*.so</span></tt> files)
wx package.</p> located in the wx package.</p>
</li> </li>
<li><p class="first">To run code with the development verison of wxPython, just set the <li><p class="first">To run code with the development verison of wxPython, just set the
PYTHONPATH to the wxPython dir in the CVS tree. For example:</p> PYTHONPATH to the wxPython dir located in the source tree. For
example:</p>
<pre class="literal-block"> <pre class="literal-block">
export LD_LIBRARY=/opt/wx/2.5/lib export LD_LIBRARY_PATH=/opt/wx/2.5/lib
export PYTHONPATH=/myprojects/wxWidgets/wxPython export PYTHONPATH=$WXDIR/wxPython
cd /myprojects/wxWidgets/wxPython/demo cd $WXDIR/wxPython/demo
python2.3 demo.py python2.3 demo.py
</pre> </pre>
<p>OS X NOTE: You need to use &quot;pythonw&quot; on the command line to run <p>OS X NOTE: You need to use &quot;pythonw&quot; on the command line to run
wxPython applications. This version of the Python executable is wxPython applications. This version of the Python executable is
part of the Python Framework and is allowed to interact with the part of the Python Framework and is allowed to interact with the
display. You can also double click on a .py or a .pyw file from display. You can also double click on a .py or a .pyw file from
the finder (assuming that PythonLauncher is still associated with the finder (assuming that the PythonLauncher app is associated with
these file extensions) and it will launch the Framework version of these file extensions) and it will launch the Framework version of
Python for you. For information about creating Applicaiton Bundles Python for you. For information about creating Applicaiton Bundles
of your wxPython apps please see the wiki and the mail lists.</p> of your wxPython apps please see the wiki and the mail lists.</p>
@@ -197,10 +207,11 @@ modules using that compiler, and then make a few changes to setup.py
to accomodate that. (And send the patches to me.) If you plan on to accomodate that. (And send the patches to me.) If you plan on
using VisualStudio.Net (a.k.a. MSVC 7.1) keep in mind that you'll also using VisualStudio.Net (a.k.a. MSVC 7.1) keep in mind that you'll also
have to build Python and any other extension modules that you use with have to build Python and any other extension modules that you use with
that compiler because a different version of the C runtime likbrary is that compiler because a different version of the C runtime library is
used. The Python executable that comes from PythonLabs and the used. The Python executable that comes from PythonLabs and the
wxPython extensions that I distribute are built with MSVC 6 with all wxPython extensions that I distribute are built with MSVC 6 with all
the Service Packs applied.</p> the Service Packs applied. This policy will change with Python 2.4
and MSVC 7.1 will be used starting with that version.</p>
<p>If you want to build a debugable version of wxWidgets and wxPython you <p>If you want to build a debugable version of wxWidgets and wxPython you
will need to have also built a debug version of Python and any other will need to have also built a debug version of Python and any other
extension modules you need to use. You can tell if you have them extension modules you need to use. You can tell if you have them
@@ -211,25 +222,28 @@ version is fine, and you can use the regular python executables with
it.</p> it.</p>
<p>Just like the unix versions I also use some scripts to help me build <p>Just like the unix versions I also use some scripts to help me build
wxWidgets, but I use some non-standard stuff to do it. So if you want wxWidgets, but I use some non-standard stuff to do it. So if you want
to use them too you'll need to get a copy or 4DOS or 4NT from to use my scripts you'll need to get a copy or 4DOS or 4NT from
<a class="reference" href="http://www.jpsoft.com/">http://www.jpsoft.com/</a> and also a copy of unix-like cat and sed <a class="reference" href="http://www.jpsoft.com/">http://www.jpsoft.com/</a> and also a copy of unix-like cat and sed
programs. You can also do by hand what my scripts are doing, but programs. You can also do by hand what my scripts are doing, but
there are a lof steps involved and I won't be going into details there are alot of steps involved and I won't be going into details
here. There is a copy of my build scripts in wxWidgetswxPythondistribmsw</p> here. There is a copy of my build scripts in %WXDIR%wxPythondistribmsw
that you can use for reference (if you don't use them directly) for
adapting these instructions to your specific needs. The directions
below assume that you are using my scripts.</p>
<ol class="arabic"> <ol class="arabic">
<li><p class="first">Set an environment variable to the root of the wxWidgets source <li><p class="first">Set an environment variable to the root of the wxWidgets source
tree:</p> tree. This is used by the makefiles:</p>
<pre class="literal-block"> <pre class="literal-block">
set WXWIN=e:\projects\wxWidgets set WXWIN=%WXDIR%
</pre> </pre>
</li> </li>
<li><p class="first">Copy setup0.h to setup.h</p> <li><p class="first">Copy setup0.h to setup.h</p>
<blockquote> <blockquote>
<p>cd %WXWIN%includewxmsw <p>cd %WXDIR%includewxmsw
copy setup0.h setup.h</p> copy setup0.h setup.h</p>
</blockquote> </blockquote>
</li> </li>
<li><p class="first">Edit %WXWIN%includewxmswsetup.h and change a few settings. <li><p class="first">Edit %WXDIR%includewxmswsetup.h and change a few settings.
Some of them are changed by my build scripts depending on the type Some of them are changed by my build scripts depending on the type
of build (debug/hybrid, unicode/ansi). I change a few of the other of build (debug/hybrid, unicode/ansi). I change a few of the other
defaults to have these values:</p> defaults to have these values:</p>
@@ -244,12 +258,13 @@ wxUSE_AFM_FOR_POSTSCRIPT 0
wxUSE_DISPLAY 1 wxUSE_DISPLAY 1
</pre> </pre>
</li> </li>
<li><p class="first">Make sure that %WXWIN%libvc_dll directory is on the PATH. The <li><p class="first">Make sure that %WXDIR%libvc_dll directory is on the PATH. The
wxWidgets DLLs will end up there as part of the build and so you'll wxWidgets DLLs will end up there as part of the build and so you'll
need it on the PATH for them to be found at runtime.</p> need it on the PATH for them to be found at runtime.</p>
</li> </li>
<li><p class="first">Change to the %WXWIN%buildmsw directory and copy my build scripts <li><p class="first">Change to the %WXDIR%buildmsw directory and copy my build scripts
there.</p> there from their default location in %WXDIR%wxPythondistribmsw
if they are not present already.</p>
</li> </li>
<li><p class="first">Use the .make.btm command to build wxWidgets. It needs one <li><p class="first">Use the .make.btm command to build wxWidgets. It needs one
command-line parameter which controls what kind of build(s) to do. command-line parameter which controls what kind of build(s) to do.
@@ -285,11 +300,11 @@ installed version of the latest release. You'll be able to test
with this version when you want to, and use the installed release with this version when you want to, and use the installed release
version the rest of the time. If you ever do want to install the version the rest of the time. If you ever do want to install the
development verison please refer to INSTALL.txt.</p> development verison please refer to INSTALL.txt.</p>
<p>Change to the wxWidgetswxPython dir and run the this command, <p>Change to the %WXDIR%wxPython dir and run the this command,
makeing sure that you use the version of python that you want to makeing sure that you use the version of python that you want to
build for (if you have more than one on your system):</p> build for (if you have more than one on your system):</p>
<pre class="literal-block"> <pre class="literal-block">
cd %WXWIN%\wxPython cd %WXDIR%\wxPython
python setup.py build_ext --inplace python setup.py build_ext --inplace
</pre> </pre>
<p>If you are wanting to have the source files regenerated with swig, <p>If you are wanting to have the source files regenerated with swig,
@@ -309,15 +324,15 @@ command line. You should then end up with a set of <tt class="literal"><span cl
files in the wx package and you'll have to run <tt class="literal"><span class="pre">python_d.exe</span></tt> to files in the wx package and you'll have to run <tt class="literal"><span class="pre">python_d.exe</span></tt> to
use them. The debug and hybrid(release) versions can coexist.</p> use them. The debug and hybrid(release) versions can coexist.</p>
<p>When the setup.py command is done you should have fully populated <p>When the setup.py command is done you should have fully populated
wxPython and wx packages locally in wxWidgets/wxPython/wxPython and wxPython and wx packages locally in %WXDIR%/wxPython/wxPython and
wxWidgets/wxPython/wx, with all the extension modules (<tt class="literal"><span class="pre">*.pyd</span></tt> %WXDIR%/wxPython/wx, with all the extension modules (<tt class="literal"><span class="pre">*.pyd</span></tt>
files) located in the wx package.</p> files) located in the wx package.</p>
</li> </li>
<li><p class="first">To run code with the development verison of wxPython, just set the <li><p class="first">To run code with the development verison of wxPython, just set the
PYTHONPATH to the wxPython dir in the CVS tree. For example:</p> PYTHONPATH to the wxPython dir in the CVS tree. For example:</p>
<pre class="literal-block"> <pre class="literal-block">
set PYTHONPATH=e:\projects\wxWidgets\wxPython set PYTHONPATH=%WXDIR%\wxPython
cd e:\projects\wxWidgets\wxPython cd %WXDIR\wxPython\demo
python demo.py python demo.py
</pre> </pre>
</li> </li>

92
wxPython/docs/BUILD.txt
View File

@@ -12,11 +12,14 @@ importantly, that you know what you are doing! ;-)
If you want to also install the version of wxPython you build to be in If you want to also install the version of wxPython you build to be in
your site-packages dir and be your default version of wxPython, then a your site-packages dir and be your default version of wxPython, then a
few additional steps are needed, and you may want to use slightly few additional steps are needed, and you may want to use slightly
different options. See INSTALL.txt for more details. If you only use different options. See the INSTALL_ document for more details. If
the instructions in this BUILD.txt file then you will end up with a you only use the instructions in this BUILD_ document file then you
separate installation of wxPython and you can switch back and forth will end up with a separate installation of wxPython and you can
between this and the release version that you may already have switch back and forth between this and the release version that you
installed. may already have installed.
.. _INSTALL: INSTALL.html
.. _BUILD: BUILD.html
If you want to make changes to any of the ``*.i`` files, (SWIG interface If you want to make changes to any of the ``*.i`` files, (SWIG interface
definition files,) or to regenerate the extension sources or renamer definition files,) or to regenerate the extension sources or renamer
@@ -31,6 +34,13 @@ command-line variable named SWIG to be the full path name of the
executable and the wxPython build will use it. See below for an executable and the wxPython build will use it. See below for an
example. example.
In the text below I'll use WXDIR with environment variable syntax
(either $WXDIR or %WXDIR%) to refer to the top level directory were
your wxWidgerts and wxPython sources are located. It will equate to
whereever you checked out the wxWidgets module from CVS, or untarred
the wxPythonSrc tarball to. You can either substitute the $WXDIR text
below with your actual dir, or set the value in the environment and
use it just like you see it below.
@@ -51,6 +61,7 @@ place, then do the same for wxPython.
rerun the script without having to remember the options I used rerun the script without having to remember the options I used
before:: before::
cd $WXDIR
mkdir bld mkdir bld
cd bld cd bld
../configure --prefix=/opt/wx/2.5 \ ../configure --prefix=/opt/wx/2.5 \
@@ -116,10 +127,11 @@ place, then do the same for wxPython.
3. I also have a script to help me build wxPython and it is checked in 3. I also have a script to help me build wxPython and it is checked in
to the CVS as wxWidgets/wxPython/b, but probably don't want to use to the CVS as wxWidgets/wxPython/b, but you probably don't want to
it as it's very cryptic and expects that you want to run SWIG, so use it as it's very cryptic and expects that you want to run SWIG,
if you don't have the latest patched up version of SWIG then you'll so if you don't have the latest patched up version of SWIG then
probably get stuck. So I'll just give the raw commands instead. you'll probably get stuck. So I'll just give the raw commands
instead.
We're not going to install the development version of wxPython with We're not going to install the development version of wxPython with
these commands, so it won't impact your already installed version these commands, so it won't impact your already installed version
@@ -134,10 +146,10 @@ place, then do the same for wxPython.
using python2.3. using python2.3.
Make sure that the first wx-config found on the PATH is the one you Make sure that the first wx-config found on the PATH is the one you
installed above, and then change to the wxWidgets/wxPython dir and installed above, and then change to the $WXDIR/wxPython dir and
run the this command:: run the this command::
cd wxPython cd $WXDIR/wxPython
python2.3 setup.py build_ext --inplace --debug python2.3 setup.py build_ext --inplace --debug
If your new wx-config script is not on the PATH, or there is some If your new wx-config script is not on the PATH, or there is some
@@ -163,24 +175,25 @@ place, then do the same for wxPython.
module. module.
When the setup.py command is done you should have fully populated When the setup.py command is done you should have fully populated
wxPython and wx packages locally in wxWidgets/wxPython/wxPython and wxPython and wx packages locally in $WXDIR/wxPython/wxPython and
.../wx, with all the extension modules (``*.so`` files) located in the $WXDIR/wxPython/wx, with all the extension modules (``*.so`` files)
wx package. located in the wx package.
4. To run code with the development verison of wxPython, just set the 4. To run code with the development verison of wxPython, just set the
PYTHONPATH to the wxPython dir in the CVS tree. For example:: PYTHONPATH to the wxPython dir located in the source tree. For
example::
export LD_LIBRARY=/opt/wx/2.5/lib export LD_LIBRARY_PATH=/opt/wx/2.5/lib
export PYTHONPATH=/myprojects/wxWidgets/wxPython export PYTHONPATH=$WXDIR/wxPython
cd /myprojects/wxWidgets/wxPython/demo cd $WXDIR/wxPython/demo
python2.3 demo.py python2.3 demo.py
OS X NOTE: You need to use "pythonw" on the command line to run OS X NOTE: You need to use "pythonw" on the command line to run
wxPython applications. This version of the Python executable is wxPython applications. This version of the Python executable is
part of the Python Framework and is allowed to interact with the part of the Python Framework and is allowed to interact with the
display. You can also double click on a .py or a .pyw file from display. You can also double click on a .py or a .pyw file from
the finder (assuming that PythonLauncher is still associated with the finder (assuming that the PythonLauncher app is associated with
these file extensions) and it will launch the Framework version of these file extensions) and it will launch the Framework version of
Python for you. For information about creating Applicaiton Bundles Python for you. For information about creating Applicaiton Bundles
of your wxPython apps please see the wiki and the mail lists. of your wxPython apps please see the wiki and the mail lists.
@@ -207,10 +220,11 @@ modules using that compiler, and then make a few changes to setup.py
to accomodate that. (And send the patches to me.) If you plan on to accomodate that. (And send the patches to me.) If you plan on
using VisualStudio.Net (a.k.a. MSVC 7.1) keep in mind that you'll also using VisualStudio.Net (a.k.a. MSVC 7.1) keep in mind that you'll also
have to build Python and any other extension modules that you use with have to build Python and any other extension modules that you use with
that compiler because a different version of the C runtime likbrary is that compiler because a different version of the C runtime library is
used. The Python executable that comes from PythonLabs and the used. The Python executable that comes from PythonLabs and the
wxPython extensions that I distribute are built with MSVC 6 with all wxPython extensions that I distribute are built with MSVC 6 with all
the Service Packs applied. the Service Packs applied. This policy will change with Python 2.4
and MSVC 7.1 will be used starting with that version.
If you want to build a debugable version of wxWidgets and wxPython you If you want to build a debugable version of wxWidgets and wxPython you
will need to have also built a debug version of Python and any other will need to have also built a debug version of Python and any other
@@ -223,25 +237,28 @@ it.
Just like the unix versions I also use some scripts to help me build Just like the unix versions I also use some scripts to help me build
wxWidgets, but I use some non-standard stuff to do it. So if you want wxWidgets, but I use some non-standard stuff to do it. So if you want
to use them too you'll need to get a copy or 4DOS or 4NT from to use my scripts you'll need to get a copy or 4DOS or 4NT from
http://www.jpsoft.com/ and also a copy of unix-like cat and sed http://www.jpsoft.com/ and also a copy of unix-like cat and sed
programs. You can also do by hand what my scripts are doing, but programs. You can also do by hand what my scripts are doing, but
there are a lof steps involved and I won't be going into details there are alot of steps involved and I won't be going into details
here. There is a copy of my build scripts in wxWidgets\wxPython\distrib\msw here. There is a copy of my build scripts in %WXDIR%\wxPython\distrib\msw
that you can use for reference (if you don't use them directly) for
adapting these instructions to your specific needs. The directions
below assume that you are using my scripts.
1. Set an environment variable to the root of the wxWidgets source 1. Set an environment variable to the root of the wxWidgets source
tree:: tree. This is used by the makefiles::
set WXWIN=e:\projects\wxWidgets set WXWIN=%WXDIR%
2. Copy setup0.h to setup.h 2. Copy setup0.h to setup.h
cd %WXWIN%\include\wx\msw cd %WXDIR%\include\wx\msw
copy setup0.h setup.h copy setup0.h setup.h
3. Edit %WXWIN%\include\wx\msw\setup.h and change a few settings. 3. Edit %WXDIR%\include\wx\msw\setup.h and change a few settings.
Some of them are changed by my build scripts depending on the type Some of them are changed by my build scripts depending on the type
of build (debug/hybrid, unicode/ansi). I change a few of the other of build (debug/hybrid, unicode/ansi). I change a few of the other
defaults to have these values:: defaults to have these values::
@@ -256,13 +273,14 @@ here. There is a copy of my build scripts in wxWidgets\wxPython\distrib\msw
wxUSE_DISPLAY 1 wxUSE_DISPLAY 1
4. Make sure that %WXWIN%\lib\vc_dll directory is on the PATH. The 4. Make sure that %WXDIR%\lib\vc_dll directory is on the PATH. The
wxWidgets DLLs will end up there as part of the build and so you'll wxWidgets DLLs will end up there as part of the build and so you'll
need it on the PATH for them to be found at runtime. need it on the PATH for them to be found at runtime.
5. Change to the %WXWIN%\build\msw directory and copy my build scripts 5. Change to the %WXDIR%\build\msw directory and copy my build scripts
there. there from their default location in %WXDIR%\wxPython\distrib\msw
if they are not present already.
6. Use the .make.btm command to build wxWidgets. It needs one 6. Use the .make.btm command to build wxWidgets. It needs one
@@ -301,11 +319,11 @@ here. There is a copy of my build scripts in wxWidgets\wxPython\distrib\msw
version the rest of the time. If you ever do want to install the version the rest of the time. If you ever do want to install the
development verison please refer to INSTALL.txt. development verison please refer to INSTALL.txt.
Change to the wxWidgets\wxPython dir and run the this command, Change to the %WXDIR%\wxPython dir and run the this command,
makeing sure that you use the version of python that you want to makeing sure that you use the version of python that you want to
build for (if you have more than one on your system):: build for (if you have more than one on your system)::
cd %WXWIN%\wxPython cd %WXDIR%\wxPython
python setup.py build_ext --inplace python setup.py build_ext --inplace
If you are wanting to have the source files regenerated with swig, If you are wanting to have the source files regenerated with swig,
@@ -326,16 +344,16 @@ here. There is a copy of my build scripts in wxWidgets\wxPython\distrib\msw
use them. The debug and hybrid(release) versions can coexist. use them. The debug and hybrid(release) versions can coexist.
When the setup.py command is done you should have fully populated When the setup.py command is done you should have fully populated
wxPython and wx packages locally in wxWidgets/wxPython/wxPython and wxPython and wx packages locally in %WXDIR%/wxPython/wxPython and
wxWidgets/wxPython/wx, with all the extension modules (``*.pyd`` %WXDIR%/wxPython/wx, with all the extension modules (``*.pyd``
files) located in the wx package. files) located in the wx package.
9. To run code with the development verison of wxPython, just set the 9. To run code with the development verison of wxPython, just set the
PYTHONPATH to the wxPython dir in the CVS tree. For example:: PYTHONPATH to the wxPython dir in the CVS tree. For example::
set PYTHONPATH=e:\projects\wxWidgets\wxPython set PYTHONPATH=%WXDIR%\wxPython
cd e:\projects\wxWidgets\wxPython cd %WXDIR\wxPython\demo
python demo.py python demo.py

16
wxPython/docs/INSTALL.html
View File

@@ -11,10 +11,10 @@
<div class="document" id="installing-wxpython-2-5-from-source"> <div class="document" id="installing-wxpython-2-5-from-source">
<h1 class="title">Installing wxPython 2.5 from Source</h1> <h1 class="title">Installing wxPython 2.5 from Source</h1>
<p>This document will describe the few differences and additions to the <p>This document will describe the few differences and additions to the
content in BUILD.txt for installing wxPython built from source. content in the <a class="reference" href="BUILD.html">BUILD</a> document for installing wxPython built from
Please follow the intstructions both in this file and in BUILD.txt to source. Please follow the intstructions both in this file and in
perform this task. Where there is overlap the items described here <a class="reference" href="BUILD.html">BUILD</a> to perform this task. Where there is overlap the items
will take precedence.</p> described here will take precedence for doing installations.</p>
<div class="section" id="installing-on-unix-like-systems-not-os-x"> <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> <h1><a name="installing-on-unix-like-systems-not-os-x">Installing on Unix-like Systems (not OS X)</a></h1>
<ol class="arabic"> <ol class="arabic">
@@ -38,10 +38,10 @@ runtime assertions turned into Python exceptions where possible.
It does add extra code to the build but probably not enough to 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 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 possible you can leave it out, but if your code does something bad
then instead of exceptions you'll likely get a crash.</p> then instead of exceptions you'll likely get a crash:</p>
<blockquote> <pre class="literal-block">
<p>--enable-debug_flag </p> --enable-debug_flag \
</blockquote> </pre>
<p>If you are building a private copy of wxWidgets (IOW, not installed <p>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 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 always have to set the LD_LIBRARY_PATH variable so wxPython can

12
wxPython/docs/INSTALL.txt
View File

@@ -3,10 +3,12 @@ Installing wxPython 2.5 from Source
This document will describe the few differences and additions to the This document will describe the few differences and additions to the
content in BUILD.txt for installing wxPython built from source. content in the BUILD_ document for installing wxPython built from
Please follow the intstructions both in this file and in BUILD.txt to source. Please follow the intstructions both in this file and in
perform this task. Where there is overlap the items described here BUILD_ to perform this task. Where there is overlap the items
will take precedence. described here will take precedence for doing installations.
.. _BUILD: BUILD.html
@@ -35,7 +37,7 @@ Installing on Unix-like Systems (not OS X)
It does add extra code to the build but probably not enough to 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 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 possible you can leave it out, but if your code does something bad
then instead of exceptions you'll likely get a crash. then instead of exceptions you'll likely get a crash::
--enable-debug_flag \ --enable-debug_flag \