-wxWindows 2.3 for Motif installation
+wxWindows 2.5 for Motif installation
------------------------------------
IMPORTANT NOTE:
If you experience problems installing, please re-read these
instructions and other related files (todo.txt, bugs.txt and
osname.txt for your platform if it exists) carefully before
- mailing wxwin-users or the author. Preferably, try to fix the
+ mailing wx-users or the author. Preferably, try to fix the
problem first and then send a patch to the author.
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.3.0, egcs 1.1.1, Redhat 5.0
+ example: wxMotif 2.5.0, gcc 2.95.4, Redhat 6.1
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 wxMotif-x.y.z.tgz, where x.y.z is the version number.
+- 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.
- 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
+ Using configure is the only 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 wx-dev@lists.wxwindows.org.
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):
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
-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 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
+mkdir buildmotif
cd buildmotif
../configure --with-motif
make
cd ..
-md buildgtk
+mkdir buildgtk
cd buildgtk
../configure --with-gtk
make
cd ..
-md buildgtkd
+mkdir buildgtkd
cd buildgtkd
-../configure --with-gtk --enable-debug_flag
+../configure --with-gtk --enable-debug
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 optimisation 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
-g++ myfoo.cpp `wx-config --libs --cflags` -o myfoo
+g++ myfoo.cpp `wx-config --libs --cxxflags` -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.
-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
-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...
+report to one of our mailing lists (see my homepage) INCLUDING A DESCRIPTION OF
+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
------------------------
+---------------
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
You can get the newest version of the Lesstif from the lesstif homepage at:
- http://www.lesstif.org
+ 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
- - Debian 2.0
+ - Debian 2.0 and 3.0
- 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
-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
+* Building wxMotif on OS/2
--------------------------
Please send comments and question about the OS/2 installation
makefile.
* Building wxMotif on SGI
---------------------------
+-------------------------
Using the SGI native compilers, it is recommended that you
also set CFLAGS and CXXFLAGS before running configure. These
The SGI native compiler support has only been tested on Irix 6.5.
* Create your configuration
------------------------------
+---------------------------
Usage:
- ./configure options
+ ./configure [options]
If you want to use system's C and C++ compiler,
set environment variables CXX and CC as
You have to add --with-motif on platforms, where Motif is
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.
--enable-dmalloc Use the dmalloc memory debugger.
Read more at www.letters.com/dmalloc/
+ --enable-debug Equivalent to --enable-debug_info plus
+ --enable-debug-flag.
+
--enable-debug_info Add debug info to object files and
executables for use with debuggers
such as gdb (or its many frontends).
options.
* Feature Options
--------------------
+-----------------
Many of the configure options have been thoroughly tested
in wxWindows snapshot 6, but not yet all (ODBC not).
--without-libjpeg Disables JPEG image format code.
-{ --without-odbc Disables ODBC code. Not yet. }
+ --without-odbc Disables ODBC code.
- --disable-resources Disables the use of *.wxr type
- resources.
-
--disable-threads Disables threads. Will also
disable sockets.
--disable-clipboard Disables Clipboard.
- --disable-serial Disables object instance serialisation.
-
--disable-streams Disables the wxStream classes.
--disable-file Disables the wxFile class.
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
make
make yourself some coffee, as it will take some time. On an old
-386SX possibly two weeks. During compilation, you'll get a few
+Pentium 200 around 40 minutes. During compilation, you may get a few
warning messages depending in your compiler.
If you want to be more selective, you can change into a specific
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
-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
$(CXX) -o minimal minimal.o `wx-config --libs`
minimal.o: minimal.cpp mondrian.xpm
- $(CXX) `wx-config --cflags` -c minimal.cpp -o minimal.o
+ $(CXX) `wx-config --cxxflags` -c minimal.cpp -o minimal.o
clean:
rm -f *.o minimal
# anyhow
# -- Julian Smart
chmod a+x configure config.sub config.guess
- ./configure --with-shared --with-motif --without-gtk --with-debug_flag --with-debug_info --enable-debug --without-threads --without-sockets --without-odbc
+ ./configure --with-shared --with-motif --with-debug_flag --with-debug_info --enable-debug --without-threads --without-sockets --without-odbc
make
-------:x-----Cut here-----:x-----
Troubleshooting
---------------
-- 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
Other Notes
-----------
-- Debugging mode is switched on by default in the makefiles, but using
- configure will create a release build of the library by default: it's
- recommended to use --with-debug_info and --with-debug_flag configure
- switches while developing your application. To compile in non-debug
- mode, remove the -D__WXDEBUG__ switch in make.env (or if using the
- configure system, change --with-debug_flag to --without_debug_flag
- and --with-debug_info to --without-debug_info in the makewxmotif
- script).
+- Using configure will create a release build of the library by
+ default: it's recommended to use --enable-debug configure switch
+ while developing your application. To compile in non-debug mode, use
+ --disable-debug configure switch.
Bug reports
-----------
projects / wxWidgets.git / blobdiff