X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/05d6c206225b4e345a3b6b625f70c147d8a11204..6a52ea5cb81dcd07c286d34b80945534780fe05f:/wxPython/docs/BUILD.html diff --git a/wxPython/docs/BUILD.html b/wxPython/docs/BUILD.html index 78e7a8ba69..dc7b3fe0bc 100644 --- a/wxPython/docs/BUILD.html +++ b/wxPython/docs/BUILD.html @@ -3,7 +3,7 @@ - + Building wxPython 2.6 for Development and Testing @@ -25,7 +25,7 @@ you only use the instructions in this BUI will end up with a separate installation of wxPython and you can switch back and forth between this and the release version that you may already have installed.

-

If you want to make changes to any of the *.i files, (SWIG +

If you want to make changes to any of the *.i files, (SWIG interface definition files,) or to regenerate the extension sources or renamer modules, then you will need an up to date version of SWIG, plus some patches. Get the sources for version 1.3.24, and then apply @@ -73,6 +73,7 @@ mkdir bld cd bld ../configure --prefix=/opt/wx/2.6 \ --with-gtk \ + --with-gnomeprint \ --with-opengl \ --enable-debug \ --enable-geometry \ @@ -81,7 +82,7 @@ cd bld --disable-debugreport \

On OS X of course you'll want to use --with-mac instead of ---with-gtk.

+--with-gtk and --with-gnomeprint.

NOTE: Due to a recent change there is currently a dependency problem in the multilib builds of wxWidgets on OSX, so I have switched to using a monolithic build. That means that all of the @@ -92,7 +93,7 @@ to the monolithic build of wxWidgets just add this configure flag:

 --enable-monolithic \
 
-

By default GTK 2.x will be used for the build. If you woudl rather +

By default GTK 2.x will be used for the build. If you would rather use GTK 1.2.x for some reason then you can force configure to use it by changing the --with-gtk flag to specify it like this:

@@ -131,7 +132,7 @@ can add these flags to the configure command:

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 +".make" (I use the leading "." so when I do rm -r * in my build dir I don't lose my scripts too.) This is what it looks like:

 make $* \
@@ -203,7 +204,7 @@ 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) +$WXDIR/wxPython/wx, with all the extension modules (*.so files) located in the wx package.

  • To run code with the development version of wxPython, just set the @@ -411,12 +412,12 @@ UNICODE=1

  • 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 +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 %WXDIR%/wxPython/wxPython and -%WXDIR%/wxPython/wx, with all the extension modules (*.pyd +%WXDIR%/wxPython/wx, with all the extension modules (*.pyd files) located in the wx package.

  • To run code with the development version of wxPython, just set the