X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/6daa06370bdb080d3555b1e0f90292489a5e64f9..dbdb39b2d0b8c3359eab1693fd1fc786499f62d7:/docs/gtk/install.txt

diff --git a/docs/gtk/install.txt b/docs/gtk/install.txt
index 728fd2f749..6aa0cd9fa1 100644
--- a/docs/gtk/install.txt
+++ b/docs/gtk/install.txt
@@ -4,17 +4,27 @@
 If you compile wxWindows on Unix for the first time and don't 
 like to read install instructions just do (in the base dir):
 
-./configure --without-threads
+./configure
 make
+make install
 
-and drink 10 coffees. Then you may log in as root and type
+* The most simple errors
+------------------------
 
-make install
+configure reports, that you don't have GTK 1.0.X installed
+although you are certainly sure you have. Well, you have
+installed it, but you also have another version of the
+GTK installed, which you may need to removed including
+other versions of glib (and its headers).
 
-You can leave out the --without-threads option if you have 
-a NEW Linux distribution based on glibc (e.g. RedHat 5.1 or 
-Debian 2.0) or any other Unix that comes with Posix threads 
-or SGI threads.
+You get errors during compilation. The reason is that you
+probably have a broken compiler, which includes almost
+everything that is called gcc. If there is just any way
+for you to use egcs, use egcs. We are sorry, but we cannot
+fix gcc for the moment.
+
+* The most simple program
+-------------------------
 
 Now create your super-application myfoo.app and compile anywhere 
 with
@@ -44,7 +54,7 @@ this has no effect, but I tried...
 
 wxWindows/GTK requires the GTK+ library to be installed on your system.
 It has to be a stable version, preferebly version 1.0.6. When using
-a version previous to 1.0.6 you'll get crashes here and there.
+a version previous to 1.0.6 you'll might get crashes here and there.
 
 wxWindows/GTK does NOT work with the 1.1.X versions of the GTK+ library
 and we will wait until the 1.2 version comes out and has stabilized
@@ -54,7 +64,7 @@ You can get the newest version of the GTK+ from the GTK homepage
 at
   http://www.gtk.org
   
-We also mirror GTK+ 1.0.6 at our ftp site. You'll find information
+We also mirror GTK+ 1.0.6 at my ftp site. You'll find information
 about downloading at my homepage.
   
 * Additional libraries
@@ -70,25 +80,28 @@ distributions have correct glibc 2 support:
  - RedHat 5.1
  - Debian 2.0
  - Stampede
+ - DLD 6.0
+ - SuSE 6.0
  
-The next major version of SuSE will also support glibc 2,
-but version 5.X does not. Also Caldera and Slackware
-don't yet support glibc 2.
-
 On IRIX you can also use SGI threads if Posix-Threads
 are not present. The SGI threads will be detected by
 configure automatically.
 
-You can always disable thread support by running 
+You can enable thread support by running 
 
-./configure "--without-threads"
+./configure "--with-threads"
 make clean
 make
+make install
   
 NB: I included thread support in wxWindows/Gtk, as this 
 problem will disappear in the near future when all major 
 Linux Variants have moved to glibc 2. Also, the Linux
-Base Standard will include glibc 2.
+Base Standard will include glibc 2 and Posix threads.
+
+NB: DO NOT COMPILE WXGTK WITH GCC AND THREADS, SINCE
+ALL PROGRAMS WILL CRASH UPON START-UP. Just always
+use egcs and be happy.
 
 * Create your configuration
 -----------------------------
@@ -146,14 +159,12 @@ toolkit. You must do this by running configure with either of:
 
         --with-gtk               Use the GIMP ToolKit (GTK)
 	
-	--with-qt                Use Qt from TrollTec
-	
 	--with-motif             Use either Motif or Lesstif
 	                         Configure will look for both. 
 
 The following options handle the kind of library you want to build.
 
-	--without-threads       Compile without thread support.
+	--with-threads          Compile without thread support.
 
 	--without-shared        Do not create shared libraries.
 
@@ -163,7 +174,6 @@ The following options handle the kind of library you want to build.
 				files. Currently broken, I think.
 				
 	--with-mem_tracing      Add built-in memory tracing. 
-	                        This doesn't work well with gcc.
 				
 	--with-dmalloc          Use the dmalloc memory debugger.
 	                        Read more at www.letters.com/dmalloc/
@@ -189,14 +199,14 @@ options (in contrast to what configure tells you).
 The following must be done in the base directory (e.g. ~/wxGTK
 or ~/wxWin or whatever)
 
-Now the makefiles are created and you can compile everything 
-by typing:
+Now the makefiles are created (by configure) and you can compile 
+the library by typing:
 
 	make
 
-make yourself some coffee, as it will try to compile ALL the 
-files in this distribution. During compilation, you'll get
-a few warning messages.
+make yourself some coffee, as it will take some time. On an old
+386SX possibly week. During compilation, you'll get a few 
+warning messages.
 
 if you want to be more selective:
 
@@ -224,6 +234,7 @@ The "global" binaries and libraries will be placed in:
 	(basedir of that application)/$(OSTYPE).
 
 This is also the place where all the object-files will go.
+(Currently there arent any global binaries).
 
 If you want to conserve disk space by removing unnecessary
 object-files: