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
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
-you know your way around your system, the compiler, etc. and that you
-know what you are doing! ;-)
+you know your way around your system, the compiler, etc. and most
+importantly, that you know what you are doing! ;-)
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
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
definition files,) or to regenerate the extension sources or renamer
modules, then you will need an up to date version of SWIG. Either get
and build the current CVS version, or version 1.3.20, and then apply
definition files,) or to regenerate the extension sources or renamer
modules, then you will need an up to date version of SWIG. Either get
and build the current CVS version, or version 1.3.20, and then apply
These platforms are built almost the same way while in development
so I'll combine the descriptions about their build process here.
These platforms are built almost the same way while in development
so I'll combine the descriptions about their build process here.
-1. Create a build directory in the main wxWindows dir, and configure
- wxWindows. If you want to have multiple builds with different
+1. Create a build directory in the main wxWidgets dir, and configure
+ wxWidgets. If you want to have multiple builds with different
configure options, just use different subdirectories. I normally
put the configure command in a script named ".configure" in each
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
before::
configure options, just use different subdirectories. I normally
put the configure command in a script named ".configure" in each
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
before::
Notice that I used a prefix of /opt/wx/2.5. 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
Notice that I used a prefix of /opt/wx/2.5. 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 wxWindows "installed" and makes it easy to switch between them,
- without impacting any versions of wxWindows that may have been
+ 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.5" with whatever prefix you
choose for your build.
If you want to use the image and zlib libraries included with
installed via an RPM or whatever. For the rest of the steps below
be sure to also substitute "/opt/wx/2.5" with whatever prefix you
choose for your build.
If you want to use the image and zlib libraries included with
example, to reduce dependencies on 3rd party libraries) then you
can add these flags to the configure command::
example, to reduce dependencies on 3rd party libraries) then you
can add these flags to the configure command::
-2. To build and install wxWindows you could just use the "make"
- command but there are other libraries besides the main wxWindows
+2. To build and install wxWidgets you could just use the "make"
+ command but there are other libraries besides the main wxWidgets
libs that also need to be built so again I make a script to do it
all for me so I don't forget anything. This time it is called
libs that also need to be built so again I make a script to do it
all for me so I don't forget anything. This time it is called
- /opt/wx/2.5 containing just wxWindows. Now to use this version of
- wxWindows you just need to add /opt/wx/2.5/bin to the PATH and set
+ /opt/wx/2.5 containing just wxWidgets. Now to use this version of
+ 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.
3. I also have a script to help me build wxPython and it is checked in
LD_LIBRARY_PATH (or DYLD_LIBRARY_PATH on OS X) to /opt/wx/2.5/lib.
3. I also have a script to help me build wxPython and it is checked in
it as it's very cryptic and expects that you want to run SWIG, so
if you don't have the latest patched up version of SWIG then you'll
probably get stuck. So I'll just give the raw commands instead.
it as it's very cryptic and expects that you want to run SWIG, so
if you don't have the latest patched up version of SWIG then you'll
probably get stuck. So I'll just give the raw commands instead.
If your new wx-config script is not on the PATH, or there is some
other version of it found first, then you can add this to the
command line to ensure your new one is used instead::
If your new wx-config script is not on the PATH, or there is some
other version of it found first, then you can add this to the
command line to ensure your new one is used instead::
If you are wanting to have the source files regenerated with swig,
then you need to turn on the USE_SWIG flag and optionally tell it
where to find the new swig executable, so add these flags::
If you are wanting to have the source files regenerated with swig,
then you need to turn on the USE_SWIG flag and optionally tell it
where to find the new swig executable, so add these flags::
If you get errors about wxGLCanvas or being unable to find libGLU
or something like that then you can add BUILD_GLCANVAS=0 to the
If you get errors about wxGLCanvas or being unable to find libGLU
or something like that then you can add BUILD_GLCANVAS=0 to the
- wxPython and wx packages locally in wxWindows/wxPython/wxPython and
- .../wx, with all the extension modules (*.so files) located in the
+ wxPython and wx packages locally in wxWidgets/wxPython/wxPython and
+ .../wx, with all the extension modules (``*.so`` files) located in the
OS X NOTE: You need to use "pythonw" on the command line to run
wxPython applications. This version of the Python executable is
part of the Python Framework and is allowed to interact with the
OS X NOTE: You need to use "pythonw" on the command line to run
wxPython applications. This version of the Python executable is
part of the Python Framework and is allowed to interact with the
the finder (assuming that PythonLauncher is still associated with
these file extensions) and it will launch the Framework version of
Python for you. For information about creating Applicaiton Bundles
the finder (assuming that PythonLauncher is still associated with
these file extensions) and it will launch the Framework version of
Python for you. For information about creating Applicaiton Bundles
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
already if there is a _d in the file names, for example python_d.exe
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
already if there is a _d in the file names, for example python_d.exe
to use them too 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
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
to use them too 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
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
of build (debug/hybrid, unicode/ansi). I change a few of the other
defaults to have these values::
of build (debug/hybrid, unicode/ansi). I change a few of the other
defaults to have these values::
-4. Make a %WXWIN%\BIN directory and add it to the PATH. My build
- scripts will copy the wxWindows DLLs there.
+4. Make sure that %WXWIN%\lib\vc_dll directory is on the PATH. The
+ 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.
- debug Build debug version
- hybrid Build hybrid version
- both Both debug and hybrid
- debug-uni Build a debug unicode library
- hybrid-uni Hybrid unicode (see the pattern yet? ;-)
- both-uni and finally both unicode libraries
+ debug Build debug version
+ hybrid Build hybrid version
+ both Both debug and hybrid
+ debug-uni Build a debug unicode library
+ hybrid-uni Hybrid unicode (see the pattern yet? ;-)
+ both-uni and finally both unicode libraries
also some of the contribs DLLs. There should be a ton of DLLs in
%WXDIR%\bin and lots of lib files and other stuff in
%WXDIR%\lib\vc_dll.
also some of the contribs DLLs. There should be a ton of DLLs in
%WXDIR%\bin and lots of lib files and other stuff in
%WXDIR%\lib\vc_dll.
version the rest of the time. If you ever do want to install the
development verison please refer to INSTALL.txt.
version the rest of the time. If you ever do want to install the
development verison please refer to INSTALL.txt.
makeing sure that you use the version of python that you want to
build for (if you have more than one on your system)::
cd %WXWIN%\wxPython
makeing sure that you use the version of python that you want to
build for (if you have more than one on your system)::
cd %WXWIN%\wxPython
If you are wanting to have the source files regenerated with swig,
then you need to turn on the USE_SWIG flag and optionally tell it
where to find the new swig executable, so add these flags::
If you are wanting to have the source files regenerated with swig,
then you need to turn on the USE_SWIG flag and optionally tell it
where to find the new swig executable, so add these flags::
- command line. You should then end up with a set of *_d.pyd files
- in the wx package and you'll have to run python_d.exe to use them.
- The debug and hybrid(release) versions can coexist.
+ command line. You should then end up with a set of ``*_d.pyd``
+ files in the wx package and you'll have to run ``python_d.exe`` to
+ use them. The debug and hybrid(release) versions can coexist.
- wxPython and wx packages locally in wxWindows/wxPython/wxPython and
- wxWindows/wxPython/wx, with all the extension modules (*.pyd files)
- located in the wx package.
+ wxPython and wx packages locally in wxWidgets/wxPython/wxPython and
+ wxWidgets/wxPython/wx, with all the extension modules (``*.pyd``
+ files) located in the wx package.
9. To run code with the development verison of wxPython, just set the
PYTHONPATH to the wxPython dir in the CVS tree. For example::
9. To run code with the development verison of wxPython, just set the
PYTHONPATH to the wxPython dir in the CVS tree. For example::
projects / wxWidgets.git / blobdiff