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

Version number changes.

Browse Source 
Added information on how to circumvent make's problems with auto-generated
        .d files.


git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@18097 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Stefan Neis
2002-12-07 15:37:00 +00:00
parent 1b6f93fcfe
commit 694f2f3cc7
1 changed files with 36 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

60
docs/os2/install.txt
View File

@@ -1,7 +1,7 @@
Installing wxWindows 2.3.4
Installing wxWindows 2.5.0
--------------------------
This is wxWindows 2.3.4 for IBM OS/2 Warp3 and Warp4. This is an unstable
This is wxWindows 2.5.0 for IBM OS/2 Warp3 and Warp4. This is an unstable
development release and OS/2 is considered to be in beta.
IMPORTANT NOTE: If you experience problems installing, please
@@ -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.3.4, copy the .zip files to there and unzip them ensuring you
C:\wx\wxWindows-2.5.0, 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;
@@ -30,7 +30,7 @@ unzip the subdirectories as well. You will need:
- PNG library source;
- ZLIB library source;
All but the documentation is included in wxOS2-2.3.4.zip, documentation
All but the documentation is included in wxOS2-2.5.0.zip, documentation
must be downloaded separately from the wxWindows Web site.
Other add-on packages are available from the wxWindows Web site, such as:
@@ -46,27 +46,27 @@ General installation notes
After unzipping everything your directory tree should look something like
this:
x:\wx\wxWindows-2.3.4\docs (your HTML reference manual)
x:\wx\wxWindows-2.3.4\include\wx
x:\wx\wxWindows-2.3.4\include\wx\generic
x:\wx\wxWindows-2.3.4\include\wx\html
x:\wx\wxWindows-2.3.4\include\wx\os2
x:\wx\wxWindows-2.3.4\samples\.... (all the sample directories)
x:\wx\wxWindows-2.3.4\src
x:\wx\wxWindows-2.3.4\src\common
x:\wx\wxWindows-2.3.4\src\generic
x:\wx\wxWindows-2.3.4\src\html
x:\wx\wxWindows-2.3.4\src\jpeg
x:\wx\wxWindows-2.3.4\src\os2
x:\wx\wxWindows-2.3.4\src\png
x:\wx\wxWindows-2.3.4\src\tiff
x:\wx\wxWindows-2.3.4\src\zlib
x:\wx\wxWindows-2.5.0\docs (your HTML reference manual)
x:\wx\wxWindows-2.5.0\include\wx
x:\wx\wxWindows-2.5.0\include\wx\generic
x:\wx\wxWindows-2.5.0\include\wx\html
x:\wx\wxWindows-2.5.0\include\wx\os2
x:\wx\wxWindows-2.5.0\samples\.... (all the sample directories)
x:\wx\wxWindows-2.5.0\src
x:\wx\wxWindows-2.5.0\src\common
x:\wx\wxWindows-2.5.0\src\generic
x:\wx\wxWindows-2.5.0\src\html
x:\wx\wxWindows-2.5.0\src\jpeg
x:\wx\wxWindows-2.5.0\src\os2
x:\wx\wxWindows-2.5.0\src\png
x:\wx\wxWindows-2.5.0\src\tiff
x:\wx\wxWindows-2.5.0\src\zlib
If you are using VisualAge, you will also need to ensure you have a
\lib directory as well, x:\wx\wxWindows-2.3.4\lib
\lib directory as well, x:\wx\wxWindows-2.5.0\lib
and you will have to set a WXWIN environment variable in your
config.sys,
SET WXWIN=X:\WX\WXWINDOWS-2.3.4;
SET WXWIN=X:\WX\WXWINDOWS-2.5.0;
Compilation
-----------
@@ -176,13 +176,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.3.4\build\pm. Now we need to set some environment
\wx\wxWindows-2.5.0\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.3.4/install-sh.
SET INSTALL=/wx/wxWindows-2.5.0/install-sh.
Be warned that depending on the precise version of your make, setting
MAKE_SHELL might not be sufficient, it might be necessary to set SHELL
@@ -201,6 +201,18 @@ directories which each essentially contain a suitable makefile.
Calling `make' now should start a compile run which hopefully ends
with a library being placed in the lib subdirectory.
Note however, that the auto-generated .d files (containing depency
information) use a mixture of "/" and "\" path separators, that
confuses many make versions. Therefore you'll often get error messages
indicating that some file with a random character in place of a path
separator cannot be found on subsequent calls to make. The only solution
currently available for this requires "sed": Run
for %1 in (*.d) do @(sed "s/\//\\/g" < %1 > dep.sed && copy dep.sed %1)
under "cmd" in the build directory (or a suitable variant of it under a
unix like shell). Note however, that a new call to make will generate
new .d files, so you will likely have to run that between any two calls
to make.
Now you can change in the samples subdirectory and call make to compile
all samples, however currently not all will work on OS/2, so you might
prefer to change into the directory of a specific sample
@@ -224,7 +236,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.3.4\build\gtk), you'll have to do a `make clean' first.
\wxWindows-2.5.0\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