new member functio of wxDbColInfo to allow two step creation , to be

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

diff --git a/docs/motif/install.txt b/docs/motif/install.txt
index 62f4bf05bd30683238c4df694618c6bcb1c5af25..4fbdde99a4301c26abea64e13160d6d068999a95 100644 (file)
--- a/docs/motif/install.txt
+++ b/docs/motif/install.txt
@@ -1,4 +1,4 @@
-wxWindows 2.1 for Motif installation
+wxWindows 2.5 for Motif installation

 ------------------------------------
 
 IMPORTANT NOTE:
 ------------------------------------
 
 IMPORTANT NOTE:


@@ -11,44 +11,40 @@ IMPORTANT NOTE:
   
   When sending bug reports tell us what version of wxWindows you are 
   using (including the beta) and what compiler on what system. One 
   
   When sending bug reports tell us what version of wxWindows you are 
   using (including the beta) and what compiler on what system. One 

-  example: wxMotif 2.1 beta 6, egcs 1.1.1, Redhat 5.0
+  example: wxMotif 2.5.0, gcc 2.95.4, Redhat 6.1

 
 First steps
 -----------
 
 
 First steps
 -----------
 

-- Prerequisites: Motif 1.2 or above, or Lesstif
-  (not yet tested). Motif 2.0 and above may also be suitable.
+- Prerequisites: Motif 1.2 or above, or Lesstif. Motif 2.0 and
+  above may also be suitable.

 
 

-- Download the appropriate .tgz archive, or alternatively the files
-  wx2_x_y_gen.zip and wx2_x_y_mot.zip. Download documentation in a preferred format,
-  such as wx2_x_y_htm.zip or wx2_x_y_pdf.zip.
+- Download wxX11-x.y.z.tgz, where x.y.z is the version number.
+  (wxMotif is included in the wxX11 distribution).
+  Download documentation in a preferred format, such as
+  wxWindows-HTML.zip or wxWindows-PDF.zip.

 
 - Make a directory such as ~/wx and unarchive the files into this
 
 - Make a directory such as ~/wx and unarchive the files into this

-  directory. If using the zip archives, use the -a option if available
-  to convert the ASCII files to Unix format. Don't worry about files being
-  overwritten: they should be identical anyway.
-
-  (See http://www.cdrom.com/pub/infozip/ if you don't have zip/unzip
-  already installed. Zip isn't the same as gzip!)
+  directory.

 
 - It is recommended that you install bison and flex; using yacc
   and lex may require tweaking of the makefiles. You also need
   libXpm (see comments in the Notes section below) if you want to have
   XPM support in wxWindows (recommended).
 
 
 - It is recommended that you install bison and flex; using yacc
   and lex may require tweaking of the makefiles. You also need
   libXpm (see comments in the Notes section below) if you want to have
   XPM support in wxWindows (recommended).
 

-- You now have the option of using the configure-based system, or the simple
-  makefile system.
+- You can now use configure to build wxWindows and the samples.

 
   Using configure is the recommended way to build the library. If it doesn't
   work for you for whatever reason, please report it (together with detailed
   information about your platform and the (relevant part of) contents of
 
   Using configure is the recommended way to build the library. If it doesn't
   work for you for whatever reason, please report it (together with detailed
   information about your platform and the (relevant part of) contents of

-  config.log file) to wxwin-developers@wx.dent.med.uni-muenchen.de.
+  config.log file) to wx-dev@lists.wxwindows.org.
+

 
 COMPILING USING CONFIGURE
 =========================
 
 
 COMPILING USING CONFIGURE
 =========================
 

-* The most simple case
------------------------
+* The simplest case
+-------------------

 
 If you compile wxWindows on Linux for the first time and don't like to read 
 install instructions just do (in the base dir):
 
 If you compile wxWindows on Linux for the first time and don't like to read 
 install instructions just do (in the base dir):


@@ -80,13 +76,13 @@ If you want to remove wxWindows on Unix you can do this:
 
 If you want to do some more serious cross-platform programming with wxWindows, 
 such as for GTK and Motif, you can now build two complete libraries and use 
 
 If you want to do some more serious cross-platform programming with wxWindows, 
 such as for GTK and Motif, you can now build two complete libraries and use 

-them concurretly. For this end, you have to create a directory for each build 
+them concurrently. For this end, you have to create a directory for each build 

 of wxWindows - you may also want to create different versions of wxWindows
 and test them concurrently. Most typically, this would be a version configured 
 of wxWindows - you may also want to create different versions of wxWindows
 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 versions (one GTK, one Motif and a debug version of the GTK 
-source) you'd do this:
+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 versions (one GTK, one Motif and a debug
+version of the GTK source) you'd do this:

 
 md buildmotif
 cd buildmotif
 
 md buildmotif
 cd buildmotif


@@ -106,45 +102,45 @@ cd buildgtkd
 make
 cd ..
 
 make
 cd ..
 

-* The most simple errors
-------------------------
-
-You get errors during compilation: The reason is that you probably have a broken 
-compiler, which includes almost everything that is called gcc. If you use gcc 2.8 
-you have to disable optimsation as the compiler will give up with an internal 
-compiler error.
+* The simplest errors
+---------------------

 
 

-If there is just any way for you to use egcs, use egcs. We cannot fix gcc.
+You get errors during compilation: The reason is that you probably have a
+broken compiler.  GCC 2.8 and earlier versions and egcs are likely to cause
+problems due to incomplete support for C++ and optimisation bugs.  Best to use
+GCC 2.95 or later.

 
 

-You get immediate segfault when starting any sample or application: This is either 
-due to having compiled the library with different flags or options than your program - 
-typically you might have the __WXDEBUG__ option set for the library but not for your 
-program - or due to using a broken compiler (and its optimisation) such as GCC 2.8.
+You get immediate segfault when starting any sample or application: This is
+either due to having compiled the library with different flags or options than
+your program - typically you might have the __WXDEBUG__ option set for the
+library but not for your program - or due to using a compiler with optimisation
+bugs.

 
 

-* The most simple program
--------------------------
+* The simplest program
+----------------------

 
 Now create your super-application myfoo.app and compile anywhere with
 
 
 Now create your super-application myfoo.app and compile anywhere with
 

-g++ myfoo.cpp `wx-config --libs --cflags` -o myfoo
+g++ myfoo.cpp `wx-config --libs --cxxflags` -o myfoo

 
 * General
 
 * 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.

 
 

-If you have general problems with installation, read my homepage at 
+If you have general problems with installation, see the wxWindows website at 

 
 

-  http://wesley.informatik.uni-freiburg.de/~wxxt
+  http://www.wxwindows.org/

   
 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 
   
 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...
+YOUR SYSTEM AND YOUR PROBLEM, SUCH AS YOUR VERSION OF MOTIF, WXMOTIF, WHAT
+DISTRIBUTION YOU USE AND WHAT ERROR WAS REPORTED. I know this has no effect,
+but I tried...

 
 * GUI libraries
 
 * GUI libraries

------------------------
+---------------

 
 wxWindows/Motif requires the Motif library to be installed on your system. As
 an alternative, you may also use the free library "lesstif" which implements
 
 wxWindows/Motif requires the Motif library to be installed on your system. As
 an alternative, you may also use the free library "lesstif" which implements


@@ -155,33 +151,74 @@ You can get the newest version of the Lesstif from the lesstif homepage at:
   http://www.lesstif.org
   
 * Additional libraries
   http://www.lesstif.org
   
 * Additional libraries

------------------------
+----------------------

 
 

-wxWindows/Motif requires a thread library and X libraries known to work with threads. 
-This is the case on all commercial Unix-Variants and all Linux-Versions that are 
-based on glibc 2 except RedHat 5.0 which is broken in many aspects. As of writing 
-this, these Linux distributions have correct glibc 2 support:
+wxWindows/Motif requires a thread library and X libraries known to work with
+threads.  This is the case on all commercial Unix-Variants and all
+Linux-Versions that are based on glibc 2 except RedHat 5.0 which is broken in
+many aspects. As of writing this, these Linux distributions have correct glibc
+2 support:

 
  - RedHat 5.1
 
  - RedHat 5.1

- - Debian 2.0
+ - Debian 2.0 and 3.0

  - Stampede
  - DLD 6.0
  - SuSE 6.0
  
 You can disable thread support by running 
 
  - Stampede
  - DLD 6.0
  - SuSE 6.0
  
 You can disable thread support by running 
 

-./configure "--disable-threads"
+./configure --disable-threads

 make
 su <type root password>
 make install
 ldconfig
 exit
   
 make
 su <type root password>
 make install
 ldconfig
 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 wxMotif 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
 
 * Building wxMotif on SGI

---------------------------
+-------------------------

 
 Using the SGI native compilers, it is recommended that you
 also set CFLAGS and CXXFLAGS before running configure. These 
 
 Using the SGI native compilers, it is recommended that you
 also set CFLAGS and CXXFLAGS before running configure. These 


@@ -199,16 +236,16 @@ untested).
 The SGI native compiler support has only been tested on Irix 6.5.
 
 * Create your configuration
 The SGI native compiler support has only been tested on Irix 6.5.
 
 * Create your configuration

------------------------------
+---------------------------

 
 Usage:
 
 Usage:

-       ./configure options
+       ./configure [options]

 
 If you want to use system's C and C++ compiler,
 
 If you want to use system's C and C++ compiler,

-set environment variables CC and CCC as
+set environment variables CXX and CC as

 
        % setenv CC cc
 
        % setenv CC cc

-       % setenv CCC CC
+       % setenv CXX CC

        % ./configure options
 
 to see all the options please use:
        % ./configure options
 
 to see all the options please use:


@@ -236,14 +273,12 @@ 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.
 
 i.e. if it says "--disable-threads" it means that threads
 are enabled by default.
 

-Many of the confiugre options have been thoroughly tested
+Many of the configure options have been thoroughly tested

 in wxWindows snapshot 6, but not yet all (ODBC not).
 
 You have to add --with-motif on platforms, where Motif is
 in wxWindows snapshot 6, but not yet all (ODBC not).
 
 You have to add --with-motif on platforms, where Motif is

-not the default (on Linux, configure will deafult to GTK).
+not the default (on Linux, configure will default to GTK).

 
 

-        --without-gtk            Don't use the GIMP ToolKit (GTK)
-       

        --with-motif             Use either Motif or Lesstif
                                 Configure will look for both. 
 
        --with-motif             Use either Motif or Lesstif
                                 Configure will look for both. 
 


@@ -278,9 +313,10 @@ The following options handle the kind of library you want to build.
        --enable-no_deps        Enable compilation without creation of
                                dependency information.
                                
        --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-permissive     Enable compilation without checking for strict
+                                ANSI conformance.  Useful to prevent the build
+                                dying with errors as soon as you compile with
+                                Solaris' ANSI-defying headers.

                                
        --enable-mem_tracing    Add built-in memory tracing. 
                                
                                
        --enable-mem_tracing    Add built-in memory tracing. 
                                


@@ -300,9 +336,9 @@ The following options handle the kind of library you want to build.
                                options.
 
 * Feature Options
                                options.
 
 * Feature Options

--------------------
+-----------------

 
 

-Many of the confiugre options have been thoroughly tested
+Many of the configure 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
 in wxWindows snapshot 6, but not yet all (ODBC not).
 
 When producing an executable that is linked statically with wxGTK


@@ -315,7 +351,7 @@ are
        
        --without-libjpeg       Disables JPEG image format code.
        
        
        --without-libjpeg       Disables JPEG image format code.
        

-       --without-odbc          Disables ODBC code.
+{      --without-odbc          Disables ODBC code. Not yet. }

        
         --disable-resources     Disables the use of *.wxr type
                                resources.
        
         --disable-resources     Disables the use of *.wxr type
                                resources.


@@ -329,7 +365,7 @@ are
        
        --disable-clipboard     Disables Clipboard.
        
        
        --disable-clipboard     Disables Clipboard.
        

-       --disable-serial        Disables object instance serialiasation.
+       --disable-serial        Disables object instance serialisation.

        
        --disable-streams       Disables the wxStream classes.
        
        
        --disable-streams       Disables the wxStream classes.
        


@@ -348,9 +384,9 @@ the program of its debugging information resulting in a significant
 reduction in size.
 
 * Compiling
 reduction in size.
 
 * Compiling

--------------
+-----------

 
 

-The following must be done in the base directory (e.g. ~/wxGTK
+The following must be done in the base directory (e.g. ~/wxMotif

 or ~/wxWin or whatever)
 
 Now the makefiles are created (by configure) and you can compile 
 or ~/wxWin or whatever)
 
 Now the makefiles are created (by configure) and you can compile 


@@ -363,9 +399,9 @@ make yourself some coffee, as it will take some time. On an old
 warning messages depending in your compiler.
 
 If you want to be more selective, you can change into a specific
 warning messages depending in your compiler.
 
 If you want to be more selective, you can change into a specific

-directiry and type "make" there.
+directory and type "make" there.

 
 

-Then you may install the library and it's header files under
+Then you may install the library and its header files under

 /usr/local/include/wx and /usr/local/lib respectively. You
 have to log in as root (i.e. run "su" and enter the root
 password) and type
 /usr/local/include/wx and /usr/local/lib respectively. You
 have to log in as root (i.e. run "su" and enter the root
 password) and type


@@ -384,29 +420,29 @@ object-files:
 in the various directories will do the work for you.
 
 * Creating a new Project
 in the various directories will do the work for you.
 
 * Creating a new Project

---------------------------
+------------------------

 
 1) The first way uses the installed libraries and header files
 automatically using wx-config
 
 
 1) The first way uses the installed libraries and header files
 automatically using wx-config
 

-g++ myfoo.cpp `wx-config --libs` `wx-config --cflags` -o myfoo
+g++ myfoo.cpp `wx-config --libs` `wx-config --cxxflags` -o myfoo

 
 Using this way, a make file for the minimal sample would look
 like this
 
 
 Using this way, a make file for the minimal sample would look
 like this
 

-CC = g++
+CXX = g++

 
 minimal: minimal.o
 
 minimal: minimal.o

-    $(CC) -o minimal minimal.o `wx-config --libs` 
+    $(CXX) -o minimal minimal.o `wx-config --libs` 

 
 minimal.o: minimal.cpp mondrian.xpm
 
 minimal.o: minimal.cpp mondrian.xpm

-    $(CC) `wx-config --cflags` -c minimal.cpp -o minimal.o
+    $(CXX) `wx-config --cxxflags` -c minimal.cpp -o minimal.o

 
 clean: 
        rm -f *.o minimal
 
 This is certain to become the standard way unless we decide
 
 clean: 
        rm -f *.o minimal
 
 This is certain to become the standard way unless we decide

-to sitch to tmake.
+to stick to tmake.

 
 2) The other way creates a project within the source code 
 directories of wxWindows. For this endeavour, you'll need
 
 2) The other way creates a project within the source code 
 directories of wxWindows. For this endeavour, you'll need


@@ -440,54 +476,12 @@ and configure before you can type make.
   This script will build wxMotif using shared libraries. If you want to build
   a static wxWindows library, use --disable-shared.
 
   This script will build wxMotif using shared libraries. If you want to build
   a static wxWindows library, use --disable-shared.
 

-COMPILING USING MAKEFILES
-=========================
-
-- Copy the file include/wx/motif/setup0.h to include/wx/motif/setup.h and
-  edit it if you wish to enable/disable some library features
-
-- Choose a .env file from src/makeenvs that matches your
-  environment, and copy it to src/make.env. These are the
-  settings read by wxWindows for Motif makefiles.
-
-- Edit src/make.env to change options according to your local
-  environment. In particular, change WXDIR to where wxWindows is
-  found on your system, or set the WXWIN environment variable
-  before compilation, e.g.:
-
-    export WXWIN=/home/jacs/wx2
-
-  Please feel free to contribute settings files for your environment.
-
-- Change directory to src/motif and type:
-
-    make -f makefile.unx motif
-
-  This should make the library libwx_motif.a in the lib
-  directory. Note that this makefile system does not build shared
-  libraries, only static ones (that is, the wxWindows library will be
-  linked statically; to see remaining dependencies on shared libraries,
-  type e.g. ldd minimal_motif).
-
-- Make a sample, such as the minimal sample:
-
-    cd samples/minimal
-    make -f makefile.unx motif
-
-  and run the resulting minimal_motif binary.
-

 Troubleshooting
 ---------------
 
 Troubleshooting
 ---------------
 

-- If you have trouble compiling the file y_tab.c, or have strange
-  linking errors, check whether you're using a C or C++ compiler for this file.
-  You should specify a C compiler in the CCLEX variable in src/make.env.
-  You could also try using bison and flex instead of yacc and
-  lex.
-
-- Solaris compilation with gcc: if the compiler has problems with the variable argument
-  functions, try putting the gcc fixinclude file paths early in the include
-  path.
+- Solaris compilation with gcc: if the compiler has problems with the variable
+  argument functions, try putting the gcc fixinclude file paths early in the
+  include path.

 
 - If you operator-related compile errors or strange memory problems
   (for example in deletion of string arrays), set wxUSE_GLOBAL_MEMORY_OPERATORS
 
 - If you operator-related compile errors or strange memory problems
   (for example in deletion of string arrays), set wxUSE_GLOBAL_MEMORY_OPERATORS


@@ -501,15 +495,6 @@ Troubleshooting
   possible temporary workaround (comment out the final
   XtDestroyWidget from ~wxWindow in window.cpp).
 
   possible temporary workaround (comment out the final
   XtDestroyWidget from ~wxWindow in window.cpp).
 

-- If you use flex and bison instead of yacc and lex, you may need
-  to change the relevant part of src/motif/makefile.unx to read:
-
-  ../common/y_tab.c: ../common/parser.y
-     $(YACC) ../common/parser.y
-     mv ../common/parser.tab.c ../common/y_tab.c
-
-  (the 'mv' command needs to be changed)
-

 - Some compilers, such as Sun C++, may give a lot of warnings about
   virtual functions being hidden. Please ignore these, it's correct C++ syntax.
   If you find any incorrect instances, though, such as a
 - Some compilers, such as Sun C++, may give a lot of warnings about
   virtual functions being hidden. Please ignore these, it's correct C++ syntax.
   If you find any incorrect instances, though, such as a


@@ -527,41 +512,13 @@ Other Notes
   and --with-debug_info to --without-debug_info in the makewxmotif
   script).
 
   and --with-debug_info to --without-debug_info in the makewxmotif
   script).
 

-- Some classes can be switched off in include/wx/motif/setup.h,
-  if you are having trouble with a particular file. However,
-  I'd prefer you to fix the problem and send the fix to me :-) or at
-  least let me know about it.
-
-- Thread support is switched off by default in setup.h (wxUSE_THREADS)
-  because standard Unices often do not have the necessary thread library
-  installed. Please see ../docs/gtk/install.txt for more details on this.
-  The systems for which thread support is known to work are Linux with libc6
-  (a.k.a. glibc2), Solaris 2.5 and 2.6 (provided that X libraries are thread
-  safe) and, to some extent, FreeBSD 2.8 and 3.1 (any feedback on thread
-  support under FreeBSD as well as the systems not mentioned here would be
-  appreciated).
-
-- If you run into problems with a missing X11/Xpm.h header, you
-  need to install the XPM package. It can be obtained from:
-
-  ftp://ftp.x.org/contrib/libraries/xpm-3.4k.tar.gz
-  http://sunfreeware.com
-
-  You may need to modify make.env to add -I and -L options pointing to where Xpm
-  is installed and possibly change bitmap.cpp to
-  include <xpm.h> instead of <X11/xpm.h>
-
-  Alternatively, edit include/wx/motif/setup.h, set wxUSE_XPM
-  to 0, and recompile. You will not be able to load any XPMs,
-  though (currently the only supported colour bitmap format).
-

 Bug reports
 -----------
 
 Please send bug reports with a description of your environment,
 compiler and the error message(s) to the wxwin-developers mailing list at:
 
 Bug reports
 -----------
 
 Please send bug reports with a description of your environment,
 compiler and the error message(s) to the wxwin-developers mailing list at:
 

-    wxwin-developers@wx.dent.med.uni-muenchen.de
+    wx-dev@lists.wxwindows.org

 
 Julian Smart, Robert Roebling and Vadim Zeitlin, November 1999.
 
 
 Julian Smart, Robert Roebling and Vadim Zeitlin, November 1999.