* The most simple case
-----------------------
-If you compile wxWindows on Unix for the first time and don't like
-to read install instructions just do (in the base dir):
+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.
-Now create your super-application myfoo.app and compile anywhere with
+* The most simple program
+-------------------------
+
+Now create your super-application myfoo.app and compile anywhere
+with
g++ myfoo.cpp `wx-config --libs` `wx-config --cflags` -o myfoo
* General
-----------------------
-The Unix variants of wxWindows use GNU configure. If you have problems
-with your make use GNU make instead.
+The Unix variants of wxWindows use GNU configure. If you have
+problems with your make use GNU make instead.
-Read my homepage at
+If you have general problems with installation, read my
+homepage at
http://wesley.informatik.uni-freiburg.de/~wxxt
-for newest information.
+for newest information. If you still don't have any success,
+please send a bug report to one of our mailing lists (see
+my homepage) INCLUDING A DESCRIPTION OF YOUR SYSTEM AND
+YOUR PROBLEM, SUCH AS YOUR VERSION OF GTK, WXGTK, WHAT
+DISTRIBUTION YOU USE AND WHAT ERROR WAS REPORTED. I know
+this has no effect, but I tried...
* GUI libraries
-----------------------
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. This
-is certain to happen with colors in native widgets.
+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
+until we'll work with that library.
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
- 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
-----------------------------
--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.
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/
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:
(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: