Building wxPython 2.5 for Development and Testing

This file describes how I build wxWindows and wxPython while doing +

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://wxwindows.org/snapshots/, a checkout from CVS, or +snapshot from http://wxWidgets.org/snapshots/, a checkout from CVS, or one of the released wxPythonSrc-2.5.* 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! ;-)

@@ -41,11 +41,11 @@ example.

Building on Unix-like Systems (e.g. Linux and OS X)

These platforms are built almost the same way while in development so I'll combine the descriptions about their build process here. -First we will build wxWindows and install it to an out of the way +First we will build wxWidgets and install it to an out of the way place, then do the same for wxPython.

Create a build directory in the main wxWindows dir, and configure -wxWindows. If you want to have multiple builds with different +
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 @@ -60,23 +60,26 @@ cd bld --disable-monolithic \ --enable-debug \ --enable-geometry \ + --enable-sound --with-sdl \ + --enable-display \
On OS X of course you'll want to use --with-mac instead of --with-gtk. For GTK2 and unicode add:
-
-
--enable-gtk2 --enable-unicode
-
+
```
+--enable-gtk2 \
+--enable-unicode \
+
```
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 -wxWindows instead of those already installed on your system, (for +wxWidgets instead of those already installed on your system, (for example, to reduce dependencies on 3rd party libraries) then you can add these flags to the configure command:
```
@@ -86,8 +89,8 @@ can add these flags to the configure command:
 --with-zlib=builtin \
 
```
To build and install wxWindows you could just use the "make" -command but there are other libraries besides the main wxWindows +
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 ".make" (I use the leading ". so when I do rm -r * in my build @@ -106,12 +109,12 @@ the execute bit on .make first!:
.make install
When it's done you should have an installed set of files under -/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.
I also have a script to help me build wxPython and it is checked in -to the CVS as wxWindows/wxPython/b, but probably don't want to use +to the CVS as wxWidgets/wxPython/b, but probably don't want to use 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.
@@ -126,7 +129,7 @@ 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 using python2.3.

Make sure that the first wx-config found on the PATH is the one you -installed above, and then change to the wxWindows/wxPython dir and +installed above, and then change to the wxWidgets/wxPython dir and run the this command:
```
 cd wxPython
@@ -154,7 +157,7 @@ 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.
 When the setup.py command is done you should have fully populated
-wxPython and wx packages locally in wxWindows/wxPython/wxPython and
+wxPython and wx packages locally in wxWidgets/wxPython/wxPython and
 .../wx, with all the extension modules (*.so files) located in the
 wx package.
 
```

 export LD_LIBRARY=/opt/wx/2.5/lib
-export PYTHONPATH=/myprojects/wxWindows/wxPython
-cd /myprojects/wxWindows/wxPython/demo
+export PYTHONPATH=/myprojects/wxWidgets/wxPython
+cd /myprojects/wxWidgets/wxPython/demo
 python2.3 demo.py

OS X NOTE: You need to use "pythonw" on the command line to run @@ -198,7 +201,7 @@ that compiler because a different version of the C runtime likbrary is 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.

If you want to build a debugable version of wxWindows 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 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 @@ -207,17 +210,17 @@ 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 -wxWindows, 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 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 -here. There is a copy of my build scripts in wxWindowswxPythondistribmsw

Set an environment variable to the root of the wxWindows source +
Set an environment variable to the root of the wxWidgets source tree:
```
-set WXWIN=e:\projects\wxWindows
+set WXWIN=e:\projects\wxWidgets
 
```
Copy setup0.h to setup.h
@@ -238,15 +241,16 @@ wxUSE_DIALUP_MANAGER 0 wxUSE_GLCANVAS 1 wxUSE_POSTSCRIPT 1 wxUSE_AFM_FOR_POSTSCRIPT 0 +wxUSE_DISPLAY 1
Make a %WXWIN%BIN directory and add it to the PATH. My build -scripts will copy the wxWindows DLLs there.
+scripts will copy the wxWidgets DLLs there.
Change to the %WXWIN%buildmsw directory and copy my build scripts there.
Use the .make.btm command to build wxWindows. It needs one +
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:
```
@@ -268,7 +272,7 @@ clean up the build::
      .make hybrid clean
 
```
When that is done it will have built the main wxWindows DLLs and +

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.

@@ -280,7 +284,7 @@ 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 wxWindowswxPython dir and run the this command, +

Change to the wxWidgetswxPython dir and run the this command, makeing sure that you use the version of python that you want to build for (if you have more than one on your system):

@@ -293,26 +297,26 @@ where to find the new swig executable, so add these flags:
  USE_SWIG=1 SWIG=e:\projects\SWIG-cvs\swig.exe
 
-If you built a Unicode version of wxWindows and want to also build
+
If you built a Unicode version of wxWidgets and want to also build
 the Unicode version of wxPython then add this flag:
  UNICODE=1
 
-If you have a debug version of Python and wxWindows and want to
+
If you have a debug version of Python and wxWidgets and want to
 build a debug version of wxPython too, add the --debug flag to the
 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.
 When the setup.py command is done you should have fully populated
-wxPython and wx packages locally in wxWindows/wxPython/wxPython and
-wxWindows/wxPython/wx, with all the extension modules (*.pyd
+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.

To run code with the development verison of wxPython, just set the PYTHONPATH to the wxPython dir in the CVS tree. For example:

-set PYTHONPATH=e:\projects\wxWindows\wxPython
-cd e:\projects\wxWindows\wxPython
+set PYTHONPATH=e:\projects\wxWidgets\wxPython
+cd e:\projects\wxWidgets\wxPython
 python demo.py

CHANGES.txt for wxPython

2.5.1.x

2.5.1.1

(See also the MigrationGuide.txt file for details about some of the big changes that have happened in this release and how you should adapt your code.)

The wxWindows project and library is now known as wxWidgets. Please +see http://www.wxwindows.org/name.htm for more details. This won't +really affect wxPython all that much, other than the fact that the +wxwindows.org domain name will be changing to wxwidgets.org, so mail +list, CVS, and etc. addresses will be changing. We're going to try +and smooth the transition as much as possible, but I wanted you all to +be aware of this change if you run into any issues.

Many, many little fixes, changes and additions done as part of the move -to wxWindows 2.5 that I have forgotten about.

+to wxWidgets 2.5 that I have forgotten about.

Added wxMirrorDC.

Added wxIconLocation

Added Python wrappers for the new wxVScrolledWindow, wxVListBox, and -wxHtmlListBox classes.

Added Python wrappers and demos for the new wxVScrolledWindow, +wxVListBox, and wxHtmlListBox classes.

Added wrappers for wxBookCtrl and wxListbook. wxNotebook now derives from wxBookCtrl.

Added Gordon Williams' PyPlot module to the library, available as the @@ -28,19 +35,19 @@ wx.lib.plot module.

I made a small but important change in the code that aquires the Python Global Interpreter Lock to try and prevent deadlocks that can happen when there are nested attempts to aquire the GIL.

The RPMs will now install menu items on Mandrake in -Applications/Development/Tools for PyCrust, XRCed, etc. They are also -installing icons and *.desktop items in the generic KDE and GNOME -locations, but I don't know yet if they are resulting in menu items on -non-Mandrake systems. (It didn't automatically do it on my RH-9 build -box but I didn't chase it very far...) If you have ideas for how to -improve the .spec file to work better and/or on more distros please -send me a patch.

The RPMs are now built on a RH-9 box, and I have tested installing -them also on my main Mandrake 9.2 box.

The RPMs will now install menu items on Mandrake Linux in +Applications/Development/Tools for PyCrust, XRCed, etc. The RPMs are +also installing icons and *.desktop items in the generic KDE and +GNOME locations, but I don't know yet if they are resulting in menu +items on non-Mandrake systems. (It didn't automatically do it on my +RH-9 build box but I didn't chase it very far...) If you have ideas +for how to improve the .spec file to work better and/or on more +distros please send me a patch.

The RPMs are now built on a fairly generic RH-9 box, and I have tested +installing them also on my main Mandrake 9.2 box.

There are some big changes in the OS X disk image. The actual Installer package now only installs the wxMac dynlibs, wxPython -extension modules and pacakges, and also the command-line tool +extension modules and Python pacakges, and also the command-line tool scripts. The remaining items (demo, samples, and application bundles for the Demo, PyCrust and XRCed) are now top-level items in the disk image (.dmg file) that users can just drag and drop to wherever they @@ -49,17 +56,26 @@ want to put them.

different API.

Updated the AnalogClockWindow with many enhancements from E. A. Tacão.

wxMac now has wx.ToggleButton!

wx.stc.StyledTextCtrl has been update to version 1.58 of Scintilla.

wx.stc.StyledTextCtrl has been updated to version 1.58 of Scintilla.

To help with the wx.stc.StyledTextCtrl performance issues on wxMac -I've added a SetUseAntiAliasing method (and GetUseAntiAliasing) too +I've added a SetUseAntiAliasing method (and GetUseAntiAliasing too) that will turn off the use of antialiased fonts in the wxSTC, allowing it to bypass the slow text measuring routines and use the fast and -simple one instead. By default the setting is turned off. When run -on OSX The Py* apps have a new item on the Options menu for -controlling this setting if you would like to experiment with it.

+simple one instead. By default the setting is turned off (on wxMac +only.) When run on OSX the Py* apps have a new item on the Options +menu for controlling this setting if you would like to experiment with +it.

Updated wx.lib.calendar with many fixes and enhancements from Joerg +"Adi" Sieker.

Added wx.Display and wx.VideoMode.

AppleEvents can be handled by overriding wx.App methods MacOpenFile, +MacPrintFile, MacNewFile, and MacReopenApp.

Added wx.PlatformInfo which is a tuple containing strings that +describe the platform and build options of wxPython. See the +MigrationGuide for more details.

2.4.2.4

Use wxSTC in the demo for displaying the soucre code of the samples.

Lots of bug fixes and such from the wxWindows folks.

Added wxPython.lib.newevent from Miki Tebeka. Its usage is @@ -68,8 +84,8 @@ demonstrated in the Threads sample in the demo.

Added wxMaskedNumCtrl.

Added Chris Barker's FloatCanvas.

2.4.1.2

Added wxScrolledPanel from Will Sadkin

Added SetShape method to top level windows (e.g. wxFrame.)

Changed wxSWIG to not generate Python code using apply, (since it will @@ -120,8 +136,8 @@ release,) SetItemMinSize can now take a wxSize (or 2-tuple) parameter, and Spacers can be specified with a wxSize (or 2-tuple) parameter

Added wxCursorFromBits.

2.4.0.7

Gave up on generating a warning upon the use of the old true/false or TRUE/FALSE values.

Fixed wxGenericTreeCtrl (used on wxGTK and wxMac for wxTreeCtrl) so @@ -151,8 +167,8 @@ think I am testing in the future...

Updated pycolourchooser.

Updated to 0.9b of PyCrust.

2.4.0.4

Added missing wxRect methods

Add OOR support for wxApp objects too.

Added wxCursorFromImage, which works on wxMSW and wxGTK so far.

@@ -208,25 +224,25 @@ doesn't have a standard place for them.

Fixed typemaps for wxGridCellCoordsArray.

Updated to the 0.9a version of PyCrust

2.4.0.2

Several bug fixes.

Added wxIntCtrl from Will Sadkin.

Added wxPyColourChooser by Michael Gilfix.

2.4.0.1

No major new features since 2.3.4.2, mostly bug fixes and minor enhancements.

Added function wrappers for the common dialogs from Kevin Altis. See wxPython/lib/dialogs.py for more details.

2.3.4.2

Various bug fixes.

2.3.4.1

Updated XRCed and wxTimeCtrl contribs.

Show a couple new wxGrid features in the demo.

Several bug fixes in wxWindows.

@@ -280,8 +296,8 @@ windows when desired.

HTMLHelp viewer does. Changed how the wxPythonDocs tarball is built and added a script to launch the doc viewer.

2.3.3.1

Added wxSplashScreen.

Added wxGenericDirCtrl.

Added wxMultiChoiceDialog.

@@ -423,15 +439,15 @@ example.

Added wxPython.lib.mixins.rubberband module from Robb Shecter.

Added wxTimeCtrl from Will Sadkin.

2.3.2.1

Changed (again) how the Python global interpreter lock is handled as well as the Python thread state. This time it works on SMP machines without barfing and is also still compatible with Python debuggers.

Added some patches from library contributors.

2.3.2

Added EVT_HELP, EVT_HELP_RANGE, EVT_DETAILED_HELP, EVT_DETAILED_HELP_RANGE, EVT_CONTEXT_MENU, wxHelpEvent, wxContextMenuEvent, wxContextHelp, wxContextHelpButton, wxTipWindow, @@ -513,8 +529,8 @@ SendCommand method, but it is still quite powerful. See wxPython/contrib/dllwidget and wxPython/demo/dllwidget for more details.

2.3.1

Added EVT_GRID_EDITOR_CREATED and wxGridEditorCreatedEvent so the user code can get access to the edit control when it is created, (to push on a custom event handler for example.)

@@ -527,8 +543,8 @@ subclass wxXmlResourceHandler, etc...

Fixed img2py to work correctly with Python 2.1.

Added enhanced wxVTKRenderWindow by Prabhu Ramachandran

2.3.0

Removed initial startup dependency on the OpenGL DLLs so only the glcanvasc.pyd depends on them, (on wxMSW.)

Changed wxFont, wxPen, wxBrush to not implicitly use the @@ -624,13 +640,13 @@ please send it to me for inclusion in this package.

by having smaller functional apps to play with. They can be found in wxPython/samples.

2.2.6

No changes happened in the Python wrappers for this release, only changes and fixes in the wxWindows library.

2.2.5

New typemaps for wxString when compiling for Python 2.0 and beyond that allow Unicode objects to be passed as well as String objects. If a Unicode object is passed PyString_AsStringAndSize is used to convert @@ -1211,7 +1227,7 @@ version segfault shortly after starting up.

diff --git a/wxPython/docs/INSTALL.html b/wxPython/docs/INSTALL.html index cc99375002..983cd11505 100644 --- a/wxPython/docs/INSTALL.html +++ b/wxPython/docs/INSTALL.html @@ -18,22 +18,22 @@ will take precedence.

Installing on Unix-like Systems (not OS X)

When building wxWindows you need to decide if you want it to be a +
When building wxWidgets you need to decide if you want it to be a private copy only accessed by wxPython, or if you would like it to be installed in a stanard location such as /usr. Or perhaps you -already have a version of wxWindows installed on your system (such +already have a version of wxWidgets installed on your system (such as from an RPM) and you want wxPython to use that version too. If so then you'll want to ensure that the flags and options used to build the installed version are compatible with wxPython.
If you do decide to build and install your own wxWindows then there +
If you do decide to build and install your own wxWidgets then there are a few tweaks to the configure flags described in BUILD.txt that you will probably want to make. Instead of --enable-debug use this configure flag:
```
 --enable-optimize \
 
```
-
Normally I also use the following flag in order to have wxWindows +
Normally I also use the following flag in order to have wxWidgets runtime assertions turned into Python exceptions where possible. 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 @@ -42,12 +42,12 @@ then instead of exceptions you'll likely get a crash.

--enable-debug_flag

-
If you are building a private copy of wxWindows (IOW, not installed +
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 always have to set the LD_LIBRARY_PATH variable so wxPython can -find the wxWindows shared libraries. You can hard code the library +find the wxWidgets shared libraries. You can hard code the library path into the binaries by using the rpath option when configuring -wxWindows. For example:
+wxWidgets. For example:
```
 --enable-rpath=/opt/wx/2.5/lib \
 
```
@@ -85,9 +85,9 @@ contained in the PYTHONPATH environment variable.
instructions above, except for a few small, but important details:
1. The --enable-rpath configure option is not needed since the path to -the wxWindows dylibs will automatically be encoded into the +the wxWidgets dylibs will automatically be encoded into the extension modules when they are built. If you end up moving the -wxWindows dynlibs to some other location (such as inside the .app +wxWidgets dynlibs to some other location (such as inside the .app bundle of your applicaiton for distribution to other users,) then you will need to set DYLD_LIBRARY_PATH to this location so the dylibs can be found at runtime.

diff --git a/wxPython/docs/README.html b/wxPython/docs/README.html index 69637d81ba..c899a28851 100644 --- a/wxPython/docs/README.html +++ b/wxPython/docs/README.html @@ -51,7 +51,7 @@ Windows.

to 2.5 that require changes to your applications

licence/* Text of the wxWindows license.

licence/* Text of the wxWidgets license.

-- Robin Dunn @@ -60,7 +60,7 @@ Robin Dunn

diff --git a/wxPython/docs/wxPackage.html b/wxPython/docs/wxPackage.html index ae84d6534c..fb8cbb71e8 100644 --- a/wxPython/docs/wxPackage.html +++ b/wxPython/docs/wxPackage.html @@ -171,7 +171,7 @@ You can learn more about these in the

diff --git a/wxPython/docs/wxPythonDocs.html b/wxPython/docs/wxPythonDocs.html index a5bfa90b2b..53eb239a9f 100644 --- a/wxPython/docs/wxPythonDocs.html +++ b/wxPython/docs/wxPythonDocs.html @@ -71,7 +71,7 @@ using the Epydoc tool.

diff --git a/wxPython/docs/wxPythonExamples.html b/wxPython/docs/wxPythonExamples.html index 5899e23d13..ef24fde165 100644 --- a/wxPython/docs/wxPythonExamples.html +++ b/wxPython/docs/wxPythonExamples.html @@ -220,7 +220,7 @@ if __name__ == '__main__':

diff --git a/wxPython/docs/wxPythonManual.html b/wxPython/docs/wxPythonManual.html index 19a4c2bd96..58672d05cb 100644 --- a/wxPython/docs/wxPythonManual.html +++ b/wxPython/docs/wxPythonManual.html @@ -1074,7 +1074,7 @@ As such, it adheres to the same license, which is provided here:

diff --git a/wxPython/docs/wxPythonTutorial.html b/wxPython/docs/wxPythonTutorial.html index 7a9ae151de..3def21c9a0 100644 --- a/wxPython/docs/wxPythonTutorial.html +++ b/wxPython/docs/wxPythonTutorial.html @@ -122,7 +122,7 @@ that comes with wxWindows: