* The most simple case
-----------------------
-If you compile wxWindows on Unix for the first time and don't like to read
+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
+
+Afterwards you can continue with
+
+> 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
-----------------
and test them concurrently. Most typically, this would be a version configured
with --enable-debug_flag and one without. Note, that only one build can currently
be installed, so you'd have to use local version of the library for that purpose.
-For building three version, one GTK, one Motif and a debug version of the GTK
-source, you'd do this:
+For building three versions (one GTK, one Motif and a debug version of the GTK
+source) you'd do this:
md buildmotif
cd buildmotif
md buildgtkd
cd buildgtkd
-../configure --with-gtk --enable-debug
+../configure --with-gtk --enable-debug_flag
make
cd ..
------------------------
configure reports, that you don't have GTK 1.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
+very sure you have. Well, you have installed it, but you also have another
+version of the GTK installed, which you may need to remove including other
versions of glib (and its headers). Also, look for the PATH variable and check
if it includes the path to the correct gtk-config! The check your LDPATH if it
points to the correct library. There is no way to compile wxGTK if configure
wxWindows/GTK requires the GTK+ library to be installed on your system. It has to
be a stable version, preferebly version 1.2.3. You can use GTK 1.0 in connection
-with wxWindows, but only without Drag'n'Drop. wxWindows does work with the 1.1.X
+with wxWindows, albeit without Drag'n'Drop. wxWindows does work with the 1.1.X
versions of the GTK+ library.
You can get the newest version of the GTK+ from the GTK homepage at:
http://www.gtk.org
-We also mirror GTK+ 1.2.1 at my ftp site soon. You'll find information about downloading
+We also mirror GTK+ 1.0.6 at my ftp site. You'll find information about downloading
at my homepage.
* Additional libraries
* General options
-------------------
-The confiugre options have not yet been thoroughly tested
-in wxWindows snapshot 6.
+Given below are the commands to change the default behaviour,
+i.e. if it says "--disable-threads" it means that threads
+are enabled by default.
+
+Many of the confiugre options have been thoroughly tested
+in wxWindows snapshot 6, but not yet all (ODBC not).
Normally, you won't have to choose a toolkit, because when
you download wxGTK, it will default to --with-gtk etc. But
if you use all of our CVS repository you have to choose a
toolkit. You must do this by running configure with either of:
- --with-gtk Use the GIMP ToolKit (GTK)
+ --without-gtk Don't use the GIMP ToolKit (GTK)
--with-motif Use either Motif or Lesstif
Configure will look for both.
--enable-profile Add profiling info to the object
files. Currently broken, I think.
+ --enable-no_rtti Enable compilation without creation of
+ C++ RTTI information in object files.
+ This will speed-up compilation and reduce
+ binary size.
+
+ --enable-no_exceptions Enable compilation without creation of
+ C++ exception information in object files.
+ This will speed-up compilation and reduce
+ 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.
* Feature Options
-------------------
-The confiugre options have not yet been thoroughly tested
-in wxWindows snapshot 6.
+Many of the confiugre options have been thoroughly tested
+in wxWindows snapshot 6, but not yet all (ODBC not).
When producing an executable that is linked statically with wxGTK
you'll be surprised at its immense size. This can sometimes be
--without-libjpeg Disables JPEG image format code.
- --without-odbc Disables ODBC code.
+{ --without-odbc Disables ODBC code. Not yet. }
- --disable-wxresources Disables the use of *.wxr type
+ --disable-resources Disables the use of *.wxr type
resources.
--disable-threads Disables threads. Will also
--disable-streams Disables the wxStream classes.
+ --disable-file Disables the wxFile class.
+
+ --disable-textfile Disables the wxTextFile class.
+
+ --disable-intl Disables the internationalisation.
+
+ --disable-validators Disables validators.
+
+ --disable-accel Disables accel.
+
Apart from disabling certain features you can very often "strip"
the program of its debugging information resulting in a significant
reduction in size.
386SX possibly two weeks. During compilation, you'll get a few
warning messages depending in your compiler.
-if you want to be more selective, you can change into a specific
+If you want to be more selective, you can change into a specific
directiry and type "make" there.
Then you may install the library and it's header files under
GNU automake version 1.4
GNU autoheader version 2.14
GNU autoconf version 2.14
+GNU libtool version 1.3
and quite possibly
GNU make
-GNU cc
+GNU C++
and if you have all this then you probably know enough to
go ahead yourself :-)
projects / wxWidgets.git / blobdiff