typo fixed

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

diff --git a/docs/motif2/install.txt b/docs/motif2/install.txt
index ecd1befffd8efbc018ec559064ca3b339085e2a0..43150cd5e7631ec4950fff7c85fa63a5991920eb 100644 (file)
--- a/docs/motif2/install.txt
+++ b/docs/motif2/install.txt
@@ -6,42 +6,30 @@
 * 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
 -----------------
@@ -148,6 +136,49 @@ exit
 NB: DO NOT COMPILE WXGTK WITH GCC AND THREADS, SINCE ALL PROGRAMS WILL CRASH UPON 
 START-UP! Just always use egcs and be happy.
 
+* Building wxGTK on OS/2
+--------------------------
+
+Please send comments and question about the OS/2 installation
+to Andrea Venturoli <a.ventu@flashnet.it> and patches to
+the wxWindows mailing list.
+
+You'll need OS/2 Warp (4.00FP#6), X-Free86/2 (3.3.3 or newer), 
+Lesstif (0.89.1 or newer), emx (0.9d fix 1), flex (2.5.4),
+yacc (1.8), unix like shell, e.g. korn shell (5.2.13),
+Autoconf (2.13),  GNU file utilities (3.6),
+GNU text utilities (1.3), GNU shell utilites (1.12), m4 (1.4), 
+sed (2.05), grep (2.0), Awk (3.0.3), GNU Make (3.76.1).
+
+Open an OS/2 prompt and switch to the directory above.
+First set some global environment variables we need:
+
+SET CXXFLAGS=-Zmtd -D__ST_MT_ERRNO__
+SET CFLAGS=-Zmtd -D__ST_MT_ERRNO__
+SET OSTYPE=OS2X              
+SET COMSPEC=sh
+
+Notice you can choose whatever you want, if you don't like OS2X.
+
+Now, run autoconf in the main directory and in the samples, demos
+and utils subdirectory. This will generate the OS/2 specific
+versions of the configure scripts. Now run
+    configure --with-motif
+as described above.
+
+To verify Lesstif installation, configure will try to compile a
+sample program that requires X headers/libraries to be either
+available via C_INCLUDE_PATH and LIBRARY_PATH or you need to
+explicitly set CFLAGS prior to running configure.
+
+If you have pthreads library installed, it will be autodetected
+and the library will be compiled with thread-support.
+
+Note that configure assumes your flex will generate files named
+"lexyy.c", not "lex.yy.c". If you have a version which does
+generate "lex.yy.c", you need to manually change the generated
+makefile.
+
 * Building wxMotif on SGI
 --------------------------
 
@@ -243,6 +274,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.
@@ -371,20 +409,10 @@ to sitch to tmake.
 
 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 :-)
 
 ----------------------