applied patch 890642: wxRE_ADVANCED flag and docs

[wxWidgets.git] / docs / tech / tn0013.txt

diff --git a/docs/tech/tn0013.txt b/docs/tech/tn0013.txt
index 7eca5935ac608f9ca6383020f62aa8c6119653e6..ac09dda044d14630d1e02396d88a8b1a145df77f 100644 (file)
--- a/docs/tech/tn0013.txt
+++ b/docs/tech/tn0013.txt
@@ -8,12 +8,15 @@ This note explains what should be done, step by step, to prepare the packages
 for a wxGTK distribution. Note that the same instructions should be used for
 the other Unix-based ports including wxMotif, wxX11 and wxBase.
 
 for a wxGTK distribution. Note that the same instructions should be used for
 the other Unix-based ports including wxMotif, wxX11 and wxBase.
 

+See distrib/msw/makerpm for a script that embodies some of the steps
+below.
+

 1. Preparing the sources
 ------------------------
 
 a) Do a fresh checkout using the command
 
 1. Preparing the sources
 ------------------------
 
 a) Do a fresh checkout using the command
 

-        cvs -d :pserver:anoncvs@cvs.wxwindows.org:/home/wxcvs co wxGTK
+        cvs -d :pserver:anoncvs@cvs.wxwindows.org:/packs/cvsroots/wxwindows co wxGTK

 
    NB: if you realize later that some needed files were not checked out
        by this command, please modify CVSROOT/modules to include the missing
 
    NB: if you realize later that some needed files were not checked out
        by this command, please modify CVSROOT/modules to include the missing


@@ -80,7 +83,7 @@ a) Setting up the RPM tree: you should have the RPM tree set up properly
    dist").
 
 b) Start RPM build by going to RPM_ROOT directory and typing "rpm -ba
    dist").
 
 b) Start RPM build by going to RPM_ROOT directory and typing "rpm -ba

-   SPECS/wxGTK.spec". It may be a good idea to append "2&>1 | tee wxGTK.out"
+   SPECS/wxGTK.spec". It may be a good idea to append "2>&1 | tee wxGTK.out"

    (or "|& tee" if you're using the one true shell ;-) as it might be not
    easy to detect errors in the verbose rpm output if anything goes wrong.
 
    (or "|& tee" if you're using the one true shell ;-) as it might be not
    easy to detect errors in the verbose rpm output if anything goes wrong.
 


@@ -96,6 +99,8 @@ b) Start RPM build by going to RPM_ROOT directory and typing "rpm -ba
    RPMS/i386/wxGTK-gl-${version}-1.i386.rpm
    RPMS/i386/wxGTK-static-${version}-1.i386.rpm
 
    RPMS/i386/wxGTK-gl-${version}-1.i386.rpm
    RPMS/i386/wxGTK-static-${version}-1.i386.rpm
 

+   Use "rpm -ba --with gtk2" to build GTK+2 version of wxGTK and use
+   "rpm -ba --with gtk2 --with unicode" to build GTK+2 Unicode build.

 
    Note: you may want to set the environment variable SMP to 3 or 4 on an
          SMP machine to speed up the build (it uses "make -j$SMP" if the
 
    Note: you may want to set the environment variable SMP to 3 or 4 on an
          SMP machine to speed up the build (it uses "make -j$SMP" if the