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

Updated information on concurrent installs.

Browse Source 
Made tab usage consistent in description of configure options.


git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@39945 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Stefan Neis
2006-07-02 22:07:39 +00:00
parent fe557b48e4
commit 5aeabc1a36
1 changed files with 43 additions and 41 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
docs/motif/install.txt
View File

@@ -79,10 +79,10 @@ 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 them concurrently. For this end, you have to create a directory for each build
of wxWidgets - you may also want to create different versions of wxWidgets of wxWidgets - you may also want to create different versions of wxWidgets
and test them concurrently. Most typically, this would be a version configured and test them concurrently. Most typically, this would be a version configured
with --enable-debug and one without. Note, that only one build can with --enable-debug and one without.
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 For building three versions (one GTK, one Motif and a debug version of the GTK
version of the GTK source) you'd do this: source) you'd do this:
mkdir buildmotif mkdir buildmotif
cd buildmotif cd buildmotif
@@ -102,6 +102,9 @@ cd buildgtkd
make make
cd .. cd ..
Note that since wxWidgets-2.6.0 you can install all those libraries
concurrently, you just need to pass the appropriate flags when using them.
* The simplest errors * The simplest errors
--------------------- ---------------------
@@ -180,9 +183,8 @@ was actually used by myself, newer version should cause no problems and
even older ones are expected to work most of the time. 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), You'll need OS/2 Warp (4.51) or eCS(1.0), X-Free86/2 (3.3.6 or newer),
Lesstif (0.92.7 or newer), emx (0.9d fix 4), flex (2.5.4), yacc (1.8) or Lesstif (0.92.7 or newer), emx (0.9d fix 4), a Unix like shell (pdksh-5.2.14
bison (1.25), a Unix like shell (pdksh-5.2.14 or ash), Autoconf (2.57), or ash), Autoconf (2.57), GNU file utilities (3.13), GNU text utilities (1.19),
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 shell utilites (1.12), m4 (1.4), sed (2.05), grep (2.0), Awk (3.0.3),
GNU Make (3.75). GNU Make (3.75).
@@ -191,15 +193,15 @@ LIBRARY_PATH set up accordingly, however, wxGTK will even work without it.
Presence of Posix/2 will be auto-detected. Presence of Posix/2 will be auto-detected.
Open an OS/2 prompt and switch to the directory above. Open an OS/2 prompt and switch to the directory above.
Set MAKESHELL (and depending on your installation also INSTALL, for me Set MAKESHELL or MAKE_SHELL (which one is needed depends on the version of
it tends to try to use the system's tcpip\pcomos\install.exe which causes make) to a Unix like shell, e.g.
problems...) to a Unix like shell, e.g.
SET MAKESHELL=ash SET MAKESHELL=ash
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 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. necessary to set SHELL or even COMSPEC to a unix like shell as well.
Depending on your installation you might want to also set INSTALL, for me
it tends to try to use the system's tcpip\pcomos\install.exe which causes
problems, e.g.
SET INSTALL=<path_to_src_directory>/install-sh -c
Notice that the delivered configure scripts are fully OS/2 aware, so you Notice that the delivered configure scripts are fully OS/2 aware, so you
can simply run can simply run