* 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 --with-motif
-make
-su <type root password>
-make install
-ldconfig
-exit
+> ./configure --with-motif
+> 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
-
-You may also want to try to edit the wrongly created libtool script
-in your build directory, if you need shared libraries on Unix. The
-wrong entries are something like
- archive_cmds="\$LD -shared ....
- archive_expsym_cmds="\$LD -shared ....
-which should be something like
- archive_cmds="\$CC -shared ....
- archive_expsym_cmds="\$CC -shared ....
+> 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
-----------------
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.
2) The other way creates a project within the source code
directories of wxWindows. For this endeavour, you'll need
-the usual number of GNU tools, at least
-
-GNU automake version 1.4
-GNU autoheader version 2.14
-GNU autoconf version 2.14
-GNU libtool version 1.2 (1.3 seems broken)
-
-and quite possibly
-
-GNU make
-GNU C++
+GNU autoconf version 2.14 and add an entry to your Makefile.in
+to the bottom of the configure.in script and run autoconf
+and configure before you can type make.
-and if you have all this then you probably know enough to
-go ahead yourself :-)
----------------------