updating docs to reflect build system changes

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@22613 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775

docs/gtk/install.txt

@@ -1,4 +1,4 @@
-wxWindows 2.4 for GTK installation
+wxWindows 2.5 for GTK installation
 ----------------------------------
 
 IMPORTANT NOTE:
@@ -44,11 +44,11 @@ If you want to remove wxWindows on Unix you can do this:
 * The GTK+ 2 case
 -----------------
 
-wxGTK 2.4.0 has support for the new version 2.0.X of GTK+. This means
-that wxGTK apps can now make use Unicode as the underlying encoding
-for all text operations. This is a very fundamental change and will
-need time to stabilize, so be careful. Anyways, after installing a
-recent version of GTK+ 2.0, do this
+wxGTK has support for the new version 2.0.X of GTK+ since version 2.4.0.
+This means that wxGTK apps can now make use Unicode as the underlying encoding
+for all text operations. This is a very fundamental change and will need time
+to stabilize, so be careful. Anyways, after installing a recent version of GTK+
+2.0, do this
 
 > ./configure --with-gtk --enable-gtk2 --enable-unicode
 > make
@@ -175,14 +175,8 @@ at my homepage.
 wxWindows/Gtk requires a thread library and X libraries known to work with
 threads.  This is the case on all commercial Unix-Variants and all
 Linux-Versions that are based on glibc 2 except RedHat 5.0 which is broken in
-many aspects. As of writing this, these Linux distributions have correct glibc
-2 support:
-
- - RedHat 5.1
- - Debian 2.0 and 3.0
- - Stampede
- - DLD 6.0
- - SuSE 6.0
+many aspects. As of writing this, virtually all Linux distributions have
+correct glibc 2 support.
 
 You can disable thread support by running
 
@@ -296,6 +290,10 @@ The following options handle the kind of library you want to build.
     --disable-shared        Do not create shared libraries, but
                             build static libraries instead.
 
+    --enable-monolithic     Build wxWindows as single library instead
+                            of as several smaller libraries (which is
+                            the default since wxWindows 2.5.0).
+
     --disable-optimise      Do not optimise the code. Can
                             sometimes be useful for debugging
                             and is required on some architectures
@@ -367,6 +365,8 @@ are
 
     --without-libtiff       Disables TIFF image format code.
 
+    --without-expat         Disable XML classes based on Expat parser.
+
     --disable-pnm           Disables PNM image format code.
 
     --disable-gif           Disables GIF image format code.
@@ -403,6 +403,10 @@ Apart from disabling certain features you can very often "strip"
 the program of its debugging information resulting in a significant
 reduction in size.
 
+Please see the output of "./configure --help" for comprehensive list
+of all configurable options.
+
+
 * Compiling
 -----------
 
@@ -464,6 +468,12 @@ clean:
 This is certain to become the standard way unless we decide
 to stick to tmake.
 
+If your application uses only some of wxWindows libraries, you can
+specify required libraries when running wx-config. For example,
+`wx-config --libs=html,core` will only output link command to link
+with libraries required by core GUI classes and wxHTML classes. See
+the manual for more information on the libraries.
+
 2) The other way creates a project within the source code
 directories of wxWindows. For this endeavour, you'll need
 GNU autoconf version 2.14 and add an entry to your Makefile.in