Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

some really ancient tips updated, mention make problems and flex version minimal requirments

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@13955 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
2002-02-01 15:30:02 +00:00
parent 376e1129f7
commit 2e1e7f9dfc
1 changed files with 164 additions and 161 deletions
Download Patch File Download Diff File Expand all files Collapse all files

73
docs/gtk/install.txt
View File

@@ -65,25 +65,36 @@ cd ..
* The most simple errors
------------------------
For any configure errors: please look at config.log file which was generated
during configure run, it usually contains some useful information.
configure reports, that you don't have GTK 1.2 installed although you are
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
doesn't pass this test as all this test does is compile and link a GTK program.
versions of glib (and its headers). Or maybe you installed it in non default
location and configure can't find it there, so please check that your PATH
variable includes the path to the correct gtk-config. Also check that your
LD_LIBRARY_PATH or equivalent variable contains the path to GTK+ libraries if
they were installed in a non default location.
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.
You get errors from make: please use GNU make instead of the native make
program. Currently wxWindows can be built only with GNU make, BSD make and
Solaris make. Other versions might work or not (any which don't have VPATH
support definitely won't).
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, which includes a lot of old gcc versions. In particular, if
you use gcc 2.8 you have to disable optimsation as the compiler will give up
with an internal compiler error.
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 broken compiler (and its
optimisation) such as gcc 2.8.
Linker complains about missing PROIO_yy_flex_alloc and similar symbols: you
probably have an old version of flex, 2.5.4 is recommended.
* The most simple program
-------------------------
@@ -110,14 +121,15 @@ YOU USE AND WHAT ERROR WAS REPORTED. I know this has no effect, but I tried...
* GUI libraries
-----------------------
wxWindows/GTK requires the GTK+ library to be installed on your system. It has to
be a stable version, preferebly version 1.2.3.
wxWindows/GTK requires the GTK+ library to be installed on your system. It has
to be a stable version, preferebly version 1.2.10 (at least 1.2.3 is required,
1.2.7 is strongly recommended).
You can get the newest version of the GTK+ from the GTK homepage at:
http://www.gtk.org
We also mirror GTK+ 1.2.3 at my ftp site. You'll find information about downloading
We also mirror GTK+ at my ftp site. You'll find information about downloading
at my homepage.
* Additional libraries
@@ -136,7 +148,7 @@ this, these Linux distributions have correct glibc 2 support:
You can disable thread support by running
./configure "--disable-threads"
./configure --disable-threads
make
su <type root password>
make install
@@ -219,18 +231,10 @@ to see all the options please use:
./configure --help
The basic philosophy is that if you want to use different
configurations, like a debug and a release version,
or use the same source tree on different systems,
you have only to change the environment variable OSTYPE.
(Sadly this variable is not set by default on some systems
in some shells - on SGI's for example). So you will have to
set it there. This variable HAS to be set before starting
configure, so that it knows which system it tries to
configure for.
Configure will complain if the system variable OSTYPE has
not been defined. And Make in some circumstances as well...
It is recommended to build wxWindows in another directory (maybe a
subdirectory of your wxWindows installation) as this allows you to
have multiple configurations (for example, debug and release or GTK
and Motif) simultaneously.
* General options
@@ -312,7 +316,8 @@ are
--with-odbc Enables ODBC code. This is disabled
by default because iODBC is under the
L-GPL license.
L-GPL license which is less liberal than
wxWindows license.
--without-libpng Disables PNG image format code.
@@ -328,11 +333,9 @@ are
--disable-iff Disables IFF image format code.
--disable-resources Disables the use of *.wxr type
resources.
--disable-resources Disables the use of *.wxr type resources.
--disable-threads Disables threads. Will also
disable sockets.
--disable-threads Disables threads. Will also disable sockets.
--disable-sockets Disables sockets.
@@ -352,7 +355,7 @@ are
--disable-validators Disables validators.
--disable-accel Disables accel.
--disable-accel Disables accelerators support.
Apart from disabling certain features you can very often "strip"
the program of its debugging information resulting in a significant