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

Added some explanation about os2-specific.zip in wxAll distribution.

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_2_4_BRANCH@18332 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Stefan Neis
2002-12-18 19:14:02 +00:00
parent 6defe40555
commit 10284f5ae6
1 changed files with 15 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
docs/os2/install.txt
View File

@@ -168,12 +168,21 @@ configure script working - the one from GNU shell utilities 1.12
does work (check that uname -s returns "OS/2" and uname -m returns "i386"
and you should be mostly fine.
The first thing to do is to decide on a build directory. You can either
do in-tree builds or you can do the build in a directory separated from
the source directory. The later has the advantage, that it is much easier
to compile and maintain several ports of wxWindows on OS/2 - if you are
developping cross-platform applications you might want to compile (and
update) e.g. wxGTK or wxX11 as well.
If you donwloaded wxAll-2.4.0, the directories will contain unix versions
of all configure scripts which need to be replaced by the OS/2 enhanced
versions contained in e.g. \wx\wxWindows-2.4.0\docs\os2\os2-specific.zip.
For this purpose change into the top level directory (\wx\wxWindows-2.4.0)
and call "unzip docs\os2\os2-specific.zip" (assuming you have InfoZip's
unzip installed). Of course, replace \wx\wxWindows-2.4.0 by the path you
did choose.
Once you are done with those preliminaries, the first thing to do is to
decide on a build directory. You can either do in-tree builds or you can
do the build in a directory separated from the source directory. The later
has the advantage, that it is much easier to compile and maintain several
ports of wxWindows on OS/2 - if you are 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.4.0\build\pm. Now we need to set some environment