If you run into what appears to be compatibility issues between +wxWidgets and wxPython while building wxPython, be sure you are using +the wxWidgets sources included with the wxPythonSrc tarball or the CVS +snapshot, and not a previously installed version or a version +installed from one of the standard wxWidgets installers. With the +"unstable" releases (have a odd-numbered minor release value, where +the APIs are allowed to change) there are often significant +differences between the W.X.Y release of wxWidgets and the W.X.Y.Z +release of wxPython.
These platforms are built almost the same way while in development @@ -131,7 +140,7 @@ instead.
these commands, so it won't impact your already installed version of the latest release. You'll be able test with this version when you want to, and use the installed release version the rest of the -time. If do want to install the development verison please read +time. If you want to install the development version please read INSTALL.txt.If you have more than one version of Python on your system then be sure to use the version of Python that you want to use when running @@ -161,16 +170,16 @@ where to find the new swig executable, so add these flags:
USE_SWIG=1 SWIG=/opt/swig/bin/swig-
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 -setup.py command line to disable the building of the glcanvas -module.
+If you get errors about being unable to find libGLU, wxGLCanvas +being undeclared, or something similar then you can add +BUILD_GLCANVAS=0 to the setup.py command line to disable the +building of the glcanvas module.
When the setup.py command is done you should have fully populated wxPython and wx packages locally in $WXDIR/wxPython/wxPython and $WXDIR/wxPython/wx, with all the extension modules (*.so files) located in the wx package.
-To run code with the development verison of wxPython, just set the +
To run code with the development version of wxPython, just set the PYTHONPATH to the wxPython dir located in the source tree. For example:
@@ -212,7 +221,7 @@ used. The Python executable that comes from PythonLabs and the wxPython extensions that I distribute are built with MSVC 6 with all 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 debuggable version of wxWidgets and wxPython you 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 @@ -221,15 +230,24 @@ of the code with the debugger then building the normal (or hybrid) version is fine, and you can use the regular python executables with it.
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 -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 -programs. You can also do by hand what my scripts are doing, but -there are alot of steps involved and I won't be going into details -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.
+wxWidgets, but I use some non-standard stuff to do it. So if you have +bash (cygwin or probably MSYS too) or 4NT plus unix-like cat and sed +programs then there is a copy of my wxWidgets build scripts in +%WXDIR%\wxPython\distrib\msw. Just copy them to +%WXDIR%\build\msw and you can use them to do your build, otherwise +you can do everything by hand as described below. But if you do work +by hand and something doesn't seem to be working correctly please +refer to the build scripts to see what may need to be done +differently. +The *.btm files are for 4NT and the others are for bash. They are:
++.make/.make.btm Builds the main lib and the needed contribs +.mymake/.mymake.btm Builds just one lib, use by .make +.makesetup.mk A makefile that will copy and edit setup.h + as needed for the different types of builds ++Okay. Here's what you've been waiting for, the instructions! Adapt +accordingly if you are using the bash shell.
Set an environment variable to the root of the wxWidgets source tree. This is used by the makefiles:
@@ -237,16 +255,13 @@ tree. This is used by the makefiles: set WXWIN=%WXDIR%
Copy setup0.h to setup.h
--+cd %WXDIR%includewxmsw -copy setup0.h setup.h
-
Copy setup0.h to setup.h:
++cd %WXDIR%\include\wx\msw +copy setup0.h setup.h +
Edit %WXDIR%includewxmswsetup.h and change a few settings. -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 -defaults to have these values:
+Edit %WXDIR%\include\wx\msw\setup.h and change a few settings:
wxDIALOG_UNIT_COMPATIBILITY 0 wxUSE_DEBUG_CONTEXT 1 @@ -257,18 +272,33 @@ wxUSE_POSTSCRIPT 1 wxUSE_AFM_FOR_POSTSCRIPT 0 wxUSE_DISPLAY 1+
If you are using my build scripts then a few more settings will be +changed and then a copy of setup.h is placed in a subdir of +%WXWIN%\libvc_dll. If you are doing it by hand and making a +UNICODE build, then also change these:
++wxUSE_UNICODE 1 +wxUSE_UNICODE_MSLU 1 ++
If you are doing a "hybrid" build (which is the same as the +binaries that I release) then also change these:
++wxUSE_MEMORY_TRACING 0 +wxUSE_DEBUG_CONTEXT 0 +
Make sure that %WXDIR%libvc_dll directory is on the PATH. The +
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 need it on the PATH for them to be found at runtime.
Change to the %WXDIR%buildmsw directory and copy my build scripts -there from their default location in %WXDIR%wxPythondistribmsw -if they are not present already.
+Change to the %WXDIR%\build\msw directory
++cd %WXDIR%\build\msw
+
Use the .make.btm command to build wxWidgets. It needs one -command-line parameter which controls what kind of build(s) to do. -Use one of the following:
+If using my scripts then use the .make.btm command to build +wxWidgets. It needs one command-line parameter which controls what +kind of build(s) to do. Use one of the following:
debug Build debug version hybrid Build hybrid version @@ -279,19 +309,46 @@ both-uni and finally both unicode libraries
For example:
- .make hybrid - -You can also pass additional command line parameters as needed and +.make hybrid ++
You can also pass additional command line parameters as needed and they will all be passed on to the nmake commands, for example to -clean up the build:: - - .make hybrid clean +clean up the build:
++.make hybrid clean ++
If not using my scripts then you can do it by hand by directly +executing nmake with a bunch of extra command line parameters. +The base set are:
++-f makefile.vc OFFICIAL_BUILD=1 SHARED=1 MONOLITHIC=0 USE_OPENGL=1 ++
If doing a debug build then add:
++BUILD=debug ++
otherwise add these:
++DEBUG_FLAG=1 CXXFLAGS=/D__NO_VC_CRTDBG__ WXDEBUGFLAG=h BUILD=release ++
If doing a Unicode build then add these flags:
++UNICODE=1 MSLU=1 ++
Now, from the %WXDIR%\build\msw directory run nmake with your +selection of command-line flags as described above. Repeat this +same command from the following directories in order to build the +contrib libraries:
++%WXDIR%\contrib\build\gizmos +%WXDIR%\contrib\build\xrc +%WXDIR%\contrib\build\stc +%WXDIR%\contrib\build\ogl
When that is done it will have built the main wxWidgets DLLs and -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%libvc_dll.
+When that is all done it will have built the main wxWidgets DLLs +and also some of the contribs DLLs. There should be a ton of DLLs +and lots of lib files and other stuff in %WXDIR%\lib\vc_dll.
Building wxPython on Windows is very similar to doing it for the unix systems. We're not going to install the development version @@ -299,9 +356,9 @@ of wxPython with these commands, so it won't impact your already installed version of the latest release. You'll be able to test 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 -development verison please refer to INSTALL.txt.
-Change to the %WXDIR%wxPython dir and run the this command, -makeing sure that you use the version of python that you want to +development version please refer to INSTALL.txt.
+Change to the %WXDIR%\wxPython dir and run the this command, +making sure that you use the version of python that you want to build for (if you have more than one on your system):
cd %WXDIR%\wxPython
@@ -328,7 +385,7 @@ wxPython and wx packages locally in %WXDIR%/wxPython/wxPython and
%WXDIR%/wxPython/wx, with all the extension modules (*.pyd
files) located in the wx package.
To run code with the development verison of wxPython, just set the +
To run code with the development version of wxPython, just set the PYTHONPATH to the wxPython dir in the CVS tree. For example:
set PYTHONPATH=%WXDIR%\wxPython