Compilation fixes

[wxWidgets.git] / utils / wxPython / BUILD.txt

diff --git a/utils/wxPython/BUILD.txt b/utils/wxPython/BUILD.txt
index 0e58de537239f9c399abd961e5dab83e5c8771ea..df6a119675f8a4060cc62656e78825d77619aa06 100644 (file)
--- a/utils/wxPython/BUILD.txt
+++ b/utils/wxPython/BUILD.txt
@@ -21,8 +21,11 @@ below.)
 
 
 1. Build and install wxWindows as described in its BuildCVS.txt or
 
 
 1. Build and install wxWindows as described in its BuildCVS.txt or

-   INSTALL.txt file.  For *nix systems I run configure with these
-   flags:
+   INSTALL.txt file.
+
+1a. Building wxWindows on Unix/Linux.
+
+   For *nix systems I run configure with these flags:

 
                 --with-gtk
                 --with-libjpeg
 
                 --with-gtk
                 --with-libjpeg


@@ -34,25 +37,56 @@ below.)
                 --enable-shared=yes
                 --disable-std_iostreams
 
                 --enable-shared=yes
                 --disable-std_iostreams
 

-   You can use whatever flags you want, but these work for me.
+   You can use whatever flags you want, but these work for me.  Be
+   sure to run "make install" to install the wxWindows headers and
+   shared library.  You can check where the wxPython build will expect
+   to find them by running "wx-config --cflags" and "wx-config --libs"
+
+1b. Building wxWindows on Win32.

 
    For Win32 systems I use Visual C++ 6.0, but 5.0 should work.  The
 
    For Win32 systems I use Visual C++ 6.0, but 5.0 should work.  The

-   build utility currently does not support any other win32
+   wxPython build utility currently does not support any other win32

    compilers.  Be sure to copy include/wx/msw/setup0.h to
    compilers.  Be sure to copy include/wx/msw/setup0.h to

-   include/wx/msw/setup.h and edit it for the options you want.
+   include/wx/msw/setup.h and edit it for the options you want.  At a
+   minimum you should set the following:
+
+          wxUSE_NEW_GRID                   0
+          wxUSE_GLOBAL_MEMORY_OPERATORS    0
+          wxUSE_LIBTIFF                    1
+
+   I also change these:
+
+          wxUSE_DIALUP_MANAGER             0
+          wxUSE_SOCKETS                    0
+          wxUSE_FS_INET                    0
+
+   There are probably other flags that can be disabled to remove
+   things not being used in wxPython, but I havn't investigated all
+   the potential configurations yet.
+
+   I find it easiest to build wxWindows using the makefiles, that way
+   I don't have to worry about what the IDE might be doing behind the
+   scenes that might screw things up.  Simply go to the src/msw
+   directory and run:
+
+   nmake -f makefile.vc CRTFLAG=/MD EXTRAFLAGS=-D__NO_VC_CRTDBG__ dll pch
+
+   If you want to make a release build, add FINAL=1 to the nmake
+   command, as well as to build.local for wxPython, (see below.)

 
 
 2. For either platform, you should be sure to set an environment
    variable named WXWIN to be the path to the top of the wxWindows
    tree.
 
 
 
 2. For either platform, you should be sure to set an environment
    variable named WXWIN to be the path to the top of the wxWindows
    tree.
 

+

 3. If you are working from a copy of the code retrieved from CVS, then
    you will find wxPython in $WXWIN/utils/wxPython.  If you are
    working from the tar.gz or .zip files then you will probably want
    to unpack wxPython in the $WXWIN/utils directory and rename the new
    directory to wxPython (or use a symlink.)  If you want to keep it
    in a separate directory then you can change where the build.py tool
 3. If you are working from a copy of the code retrieved from CVS, then
    you will find wxPython in $WXWIN/utils/wxPython.  If you are
    working from the tar.gz or .zip files then you will probably want
    to unpack wxPython in the $WXWIN/utils directory and rename the new
    directory to wxPython (or use a symlink.)  If you want to keep it
    in a separate directory then you can change where the build.py tool

-   expects to find it by creating a file named build.local (see step 6
+   expects to find it by creating a file named build.local (see step 7

    for more examples about build.local,) containing something like
    this:
 
    for more examples about build.local,) containing something like
    this:
 


@@ -60,7 +94,7 @@ below.)
 
 
 4. At this point you may want to make an alias or symlink, script,
 
 
 4. At this point you may want to make an alias or symlink, script,

-   batch file, whatever on the PATH that invokes
+   batch file, or whatever on the PATH that invokes

    $WXWIN/utils/wxPython/distrib/build.py to help simplify matters
    somewhat.  For example, on my win32 system I have a file named
    build.bat in a directory on the PATH that contains:
    $WXWIN/utils/wxPython/distrib/build.py to help simplify matters
    somewhat.  For example, on my win32 system I have a file named
    build.bat in a directory on the PATH that contains:


@@ -71,16 +105,25 @@ below.)
 5. Change into the $(WXWIN)/utils/wxPython/src directory.
 
 
 5. Change into the $(WXWIN)/utils/wxPython/src directory.
 
 

-6. Type "build -b" to build wxPython and "build -i" to install it.
+6. If you don't use SWIG, or have a new enough version installed, you
+   may have to update the timestamps of the files it generates so the
+   make utility won't think they are out of date and try to run SWIG
+   to update them.  The standard touch utility can do this for you:
+
+   touch gtk/*.cpp gtk/*.py
+
+
+7. Type "build -b" to build wxPython and "build -i" to install it.

 
    The build.py script actually generates a Makefile based on what it
    finds on your system and information found in the build.cfg file.
    If you have troubles building or you want it built or installed in
    a different way, take a look at the docstring in build.py.  You may
    be able to override configuration options in a file named
 
    The build.py script actually generates a Makefile based on what it
    finds on your system and information found in the build.cfg file.
    If you have troubles building or you want it built or installed in
    a different way, take a look at the docstring in build.py.  You may
    be able to override configuration options in a file named

-   build.local.  For example, you can set a new TARGETDIR just by
-   creating a file named build.local in your wxPython source directory
-   and assign a value to it, like this:
+   build.local.  For example, you can set a new TARGETDIR (the
+   installation directory) just by creating a file named build.local
+   in your wxPython source directory and assign a value to it, like
+   this:

 
    TARGETDIR = "/usr/local/lib/python1.5/site-packages/wxPython"
 
 
    TARGETDIR = "/usr/local/lib/python1.5/site-packages/wxPython"
 


@@ -88,20 +131,18 @@ below.)
    creative things there if you need to.
 
 
    creative things there if you need to.
 
 

-7. To build and install the add-on modules, change to the appropriate
+8. To build and install the add-on modules, change to the appropriate

    directory under $WXWIN/utils/wxPython/modules and run the build
    utility again.
 
 
    directory under $WXWIN/utils/wxPython/modules and run the build
    utility again.
 
 

-8. Change to the $WXWIN/utils/wxPython/demo directory.
+9. Change to the $WXWIN/utils/wxPython/demo directory.

 
 
 
 

-9. Try executing the demo program.  For example:
+10. Try executing the demo program.  For example:

 
     python demo.py
 
 
     python demo.py
 

-To run it without requiring a console on win32, you can use the
-pythonw.exe version of Python either from the command line or from a
-shortcut.
-
-
+    To run it without requiring a console on win32, you can use the
+    pythonw.exe version of Python either from the command line or from
+    a shortcut.