AuroraMiddleware/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fixed version number.

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@16844 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Stefan Neis 2002-08-28 17:29:28 +00:00
parent 1281c5c188
commit 0bc7468b1f
1 changed files with 21 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
docs/os2/install.txt
View File

@ -17,7 +17,7 @@ Unarchiving
At this time there is no comprehensive setup.exe type installation program.
wxWindows for OS/2 requires you download various .zip files and unpack them
to your desired location on your system. Pick a location say,
C:\wx\wxWindows-2.2.3, copy the .zip files to there and unzip them ensuring you
C:\wx\wxWindows-2.3.3, copy the .zip files to there and unzip them ensuring you
unzip the subdirectories as well. You will need:
- All common, generic and OS2-specific wxWindows source;
@ -46,27 +46,27 @@ General installation notes
After unzipping everything your directory tree should look something like
this:
x:\wx\wxWindows-2.2.3\docs (your HTML reference manual)
x:\wx\wxWindows-2.2.3\include\wx
x:\wx\wxWindows-2.2.3\include\wx\generic
x:\wx\wxWindows-2.2.3\include\wx\html
x:\wx\wxWindows-2.2.3\include\wx\os2
x:\wx\wxWindows-2.2.3\samples\.... (all the sample directories)
x:\wx\wxWindows-2.2.3\src
x:\wx\wxWindows-2.2.3\src\common
x:\wx\wxWindows-2.2.3\src\generic
x:\wx\wxWindows-2.2.3\src\html
x:\wx\wxWindows-2.2.3\src\jpeg
x:\wx\wxWindows-2.2.3\src\os2
x:\wx\wxWindows-2.2.3\src\png
x:\wx\wxWindows-2.2.3\src\tiff
x:\wx\wxWindows-2.2.3\src\zlib
x:\wx\wxWindows-2.3.3\docs (your HTML reference manual)
x:\wx\wxWindows-2.3.3\include\wx
x:\wx\wxWindows-2.3.3\include\wx\generic
x:\wx\wxWindows-2.3.3\include\wx\html
x:\wx\wxWindows-2.3.3\include\wx\os2
x:\wx\wxWindows-2.3.3\samples\.... (all the sample directories)
x:\wx\wxWindows-2.3.3\src
x:\wx\wxWindows-2.3.3\src\common
x:\wx\wxWindows-2.3.3\src\generic
x:\wx\wxWindows-2.3.3\src\html
x:\wx\wxWindows-2.3.3\src\jpeg
x:\wx\wxWindows-2.3.3\src\os2
x:\wx\wxWindows-2.3.3\src\png
x:\wx\wxWindows-2.3.3\src\tiff
x:\wx\wxWindows-2.3.3\src\zlib
If you are using VisualAge, you will also need to ensure you have a
\lib directory as well, x:\wx\wxWindows-2.2.3\lib
\lib directory as well, x:\wx\wxWindows-2.3.3\lib
and you will have to set a WXWIN environment variable in your
config.sys,
SET WXWIN=X:\WX\WXWINDOWS-2.2.3;
SET WXWIN=X:\WX\WXWINDOWS-2.3.3;
Compilation
-----------
@ -173,13 +173,13 @@ developping cross-platform applications you might want to compile (and
update) e.g. wxGTK or wxX11 as well.
In the following, let's assume you decided to build in
\wx\wxWindows-2.2.3\build\pm. Now we need to set some environment
\wx\wxWindows-2.3.3\build\pm. Now we need to set some environment
variables, namely MAKE_SHELL (to a Unix like shell, let's assume ash)
and INSTALL (to point to the install script. If you omit this, configure
might find something like the system's tcpip\pcomos\install.exe which will
not do the thing you want), e.g.
SET MAKE_SHELL=ash
SET INSTALL=/wx/wxWindows-2.2.3/install-sh.
SET INSTALL=/wx/wxWindows-2.3.3/install-sh.
Now run the provided configure script by executing e.g.
`ash -c "../../configure \
@ -217,7 +217,7 @@ Finally, if you also want to build a different port, e.g. wxGTK, you
essentially have to use the procedure described above, the only difference
being that you have to pass a switch to configure indicating which port
to build. If you do not do this in a separate build directory (e.g.
\wxWindows-2.2.3\build\gtk), you'll have to do a `make clean' first.
\wxWindows-2.3.3\build\gtk), you'll have to do a `make clean' first.
The magical switches that have to be passed to configure for the various
ports are --with-gtk (wxGTK), --with-motif (wxMotif), --with-x11 (wxX11),
and --disable-gui (wxBase). Note that contrary to the native, PM based