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

This commit was manufactured by cvs2svn to create tag

Browse Source 
'DEBIAN_2_4_3_1_SARGE_v_2_4_2_4'.

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/tags/DEBIAN_2_4_3_1_SARGE_v_2_4_2_4@34395 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Bryan Petty
2005-05-29 09:56:16 +00:00
parent 86118733af
commit cfd794784f
4010 changed files with 349688 additions and 169530 deletions
Download Patch File Download Diff File Expand all files Collapse all files

107
docs/gtk/install.txt
View File

@@ -1,4 +1,4 @@
wxWindows 2.3 for GTK installation
wxWidgets 2.4 for GTK installation
----------------------------------
IMPORTANT NOTE:
@@ -9,14 +9,14 @@ IMPORTANT NOTE:
mailing wxwin-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
When sending bug reports tell us what version of wxWidgets you are
using (including the beta) and what compiler on what system. One
example: wxGTK 2.3.3, gcc 2.95.4, Redhat 6.2
example: wxGTK 2.4.0, gcc 2.95.4, Redhat 6.2
* The simplest case
-------------------
If you compile wxWindows on Linux for the first time and don't like to read
If you compile wxWidgets on Linux for the first time and don't like to read
install instructions just do (in the base dir):
> ./configure --with-gtk
@@ -34,7 +34,7 @@ Afterwards you can continue with
> ldconfig
> exit
If you want to remove wxWindows on Unix you can do this:
If you want to remove wxWidgets on Unix you can do this:
> su <type root password>
> make uninstall
@@ -44,7 +44,7 @@ If you want to remove wxWindows on Unix you can do this:
* The GTK+ 2 case
-----------------
wxGTK 2.3.3 has support for the new version 2.0.X of GTK+. This means
wxGTK 2.4.3 has support for the new version 2.0.X of GTK+. This means
that wxGTK apps can now make use Unicode as the underlying encoding
for all text operations. This is a very fundamental change and will
need time to stabilize, so be careful. Anyways, after installing a
@@ -68,12 +68,12 @@ Expect problems.
* The expert case
-----------------
If you want to do some more serious cross-platform programming with wxWindows,
If you want to do some more serious cross-platform programming with wxWidgets,
such as for GTK and Motif, you can now build two complete libraries and use
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
of wxWidgets - you may also want to create different versions of wxWidgets
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
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.
@@ -94,7 +94,7 @@ cd ..
md buildgtkd
cd buildgtkd
../configure --with-gtk --enable-debug_flag
../configure --with-gtk --enable-debug
make
cd ..
@@ -114,7 +114,7 @@ LD_LIBRARY_PATH or equivalent variable contains the path to GTK+ libraries if
they were installed in a non default location.
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
program. Currently wxWidgets 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).
@@ -142,7 +142,7 @@ g++ myfoo.cpp `wx-config --libs --cxxflags` -o myfoo
* General
---------
The Unix variants of wxWindows use GNU configure. If you have problems with
The Unix variants of wxWidgets 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
@@ -158,7 +158,7 @@ but I tried...
* GUI libraries
---------------
wxWindows/GTK requires the GTK+ library to be installed on your system. It has
wxWidgets/GTK requires the GTK+ library to be installed on your system. It has
to be a stable version, preferably version 1.2.10 (at least 1.2.3 is required,
1.2.7 is strongly recommended).
@@ -172,7 +172,7 @@ at my homepage.
* Additional libraries
----------------------
wxWindows/Gtk requires a thread library and X libraries known to work with
wxWidgets/Gtk 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
@@ -197,39 +197,44 @@ exit
------------------------
Please send comments and question about the OS/2 installation
to Andrea Venturoli <a.ventu@flashnet.it> and patches to
the wxWindows mailing list.
to Stefan Neis <Stefan.Neis@t-online.de> and patches to
the wxWidgets mailing list.
You'll need OS/2 Warp (4.00FP#6), X-Free86/2 (3.3.3 or newer),
GTK+ (1.2.5 or newer), emx (0.9d fix 1), flex (2.5.4), yacc (1.8),
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).
In the following list, the version numbers indicate the configuration that
was actually used by myself, newer version should cause no problems and
even older ones are expected to work most of the time.
You'll need OS/2 Warp (4.51) or eCS(1.0), X-Free86/2 (3.3.6 or newer),
GTK+ (1.2.5 or newer), emx (0.9d fix 4), flex (2.5.4), yacc (1.8) or
bison (1.25), a Unix like shell (pdksh-5.2.14 or ash), Autoconf (2.57),
GNU file utilities (3.13), GNU text utilities (1.19),
GNU shell utilites (1.12), m4 (1.4), sed (2.05), grep (2.0), Awk (3.0.3),
GNU Make (3.75).
Preferably, you should have Posix/2 installed and C(PLUS)_INCLUDE_PATH and
LIBRARY_PATH set up accordingly, however, wxGTK will even work without it.
Presence of Posix/2 will be auto-detected.
Open an OS/2 prompt and switch to the directory above.
First set some global environment variables we need:
If you didn't do it yet, unzip distrib/os2/os2-specific.zip into the current
directory. This will overwrite the configure scripts in the main directory
and in the samples, demos and utils subdirectory with the OS/2 aware
versions. Alternatively, if you didn't get os2-specific.zip (e.g. because
you downloaded wxGTK only), run autoconf yourself in the said directories.
SET CXXFLAGS=-Zmtd -D__ST_MT_ERRNO__
SET CFLAGS=-Zmtd -D__ST_MT_ERRNO__
SET OSTYPE=OS2X
SET COMSPEC=sh
Set MAKESHELL (and depending on your installation also INSTALL, for me
it tends to try to use the system's tcpip\pcomos\install.exe which causes
problems...) to a Unix like shell, e.g.
SET MAKESHELL=ash
Notice you can choose whatever you want, if you don't like OS2X.
Be warned that depending on the precise version of your make, the
variable that needs to be set might be MAKE_SHELL instead of MAKESHELL.
If you have a really deficient version of GNU make, it might even be
necessary to set SHELL or even COMSPEC to a unix like shell as well.
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-gtk
as described above.
If you have pthreads library installed, but have a gtk version
which does not yet support threading, you need to explicitly
disable threading by using the option --disable-threads.
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.
Now run
ash -c "configure --with-gtk"
and make and possibly make install as described above.
* Building wxGTK on SGI
-----------------------
@@ -266,8 +271,8 @@ to see all the options please use:
./configure --help
It is recommended to build wxWindows in another directory (maybe a
subdirectory of your wxWindows installation) as this allows you to
It is recommended to build wxWidgets in another directory (maybe a
subdirectory of your wxWidgets installation) as this allows you to
have multiple configurations (for example, debug and release or GTK
and Motif) simultaneously.
@@ -334,26 +339,32 @@ The following options handle the kind of library you want to build.
such as gdb (or its many frontends).
--enable-debug_flag Define __DEBUG__ and __WXDEBUG__ when
compiling. This enable wxWindows' very
compiling. This enable wxWidgets' very
useful internal debugging tricks (such
as automatically reporting illegal calls)
to work. Note that program and library
must be compiled with the same debug
options.
--enable-debug Same as --enable-debug_info and
--enable-debug_flag together. Unless you have
some very specific needs, you should use this
option instead of --enable-debug_info/flag ones
separately.
* Feature Options
-----------------
When producing an executable that is linked statically with wxGTK
you'll be surprised at its immense size. This can sometimes be
drastically reduced by removing features from wxWindows that
drastically reduced by removing features from wxWidgets that
are not used in your program. The most relevant such features
are
--with-odbc Enables ODBC code. This is disabled
by default because iODBC is under the
L-GPL license which is less liberal than
wxWindows license.
wxWidgets license.
--without-libpng Disables PNG image format code.
@@ -422,7 +433,7 @@ password) and type
make install
You can remove any traces of wxWindows by typing
You can remove any traces of wxWidgets by typing
make uninstall
@@ -459,7 +470,7 @@ This is certain to become the standard way unless we decide
to stick to tmake.
2) The other way creates a project within the source code
directories of wxWindows. For this endeavour, you'll need
directories of wxWidgets. For this endeavour, you'll need
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.