Solved problem with wxhInstance name being mangled by MSVC; wxGetInstance is now...

[wxWidgets.git] / docs / gtk / install.txt

diff --git a/docs/gtk/install.txt b/docs/gtk/install.txt
index cbc7f33ed8fa47db5a7f34d8acef5538d5e59d1e..2c482a12e76d9f98352d8dd5ec6c68a8eb77f008 100644 (file)
--- a/docs/gtk/install.txt
+++ b/docs/gtk/install.txt
@@ -9,30 +9,27 @@
 If you compile wxWindows on Linux for the first time and don't like to read 
 install instructions just do (in the base dir):
 
-./configure
-make
-su <type root password>
-make install
-ldconfig
-exit
+> ./configure --with-gtk
+> make
+> su <type root password>
+> make install
+> ldconfig
+> exit
 
-On all other Unices (maybe except *BSD), shared libraries are not supported
-out of the box due to the utter stupidity of libtool, so you'll have to do
-this instead:
+Afterwards you can continue with
 
-./configure --enable-static --disable-shared
-make
-su <type root password>
-make install
-ldconfig
-exit
+> make
+> su <type root password>
+> make install
+> ldconfig
+> exit
 
 If you want to remove wxWindows on Unix you can do this:
 
-su <type root password>
-make uninstall
-ldconfig
-exit
+> su <type root password>
+> make uninstall
+> ldconfig
+> exit
 
 * The expert case
 -----------------
@@ -270,6 +267,13 @@ The following options handle the kind of library you want to build.
                                binary size. Also fewer crashes during the
                                actual compilation...
                                
+       --enable-no_deps        Enable compilation without creation of
+                               dependency information.
+                               
+       --enable-permissive     Enable compilation without creation of
+                               giving erros as soon as you compile with
+                               Solaris ANSI-defying headers...
+                               
        --enable-mem_tracing    Add built-in memory tracing. 
                                
        --enable-dmalloc        Use the dmalloc memory debugger.