-Installing wxWidgets 2.7.0
---------------------------
+Installing wxWidgets
+--------------------
-This is wxWidgets 2.7.0 for IBM OS/2 Warp3 and Warp4. This is an unstable
+This is wxWidgets 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
At this time there is no comprehensive setup.exe type installation program.
wxWidgets 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\wxWidgets-2.7.0, copy the .zip files to there and unzip them ensuring you
+C:\wx\wxWidgets-2.8.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 wxWidgets source;
- samples;
- documentation in HTML Help format;
- makefiles for VisualAge V3.0 (possibly for EMX and Watcom C++);
-- HTML library source;
-- JPEG library source;
-- TIFF library source;
-- PNG library source;
-- ZLIB library source;
+- JPEG, TIFF, PNG, ZLIB, wxSTC, REGEX, EXPAT library sources.
-All but the documentation is included in wxOS2-2.7.0.zip, documentation
+All but the documentation is included in wxOS2-2.8.0.zip, documentation
must be downloaded separately from the wxWidgets Web site.
-Other add-on packages are available from the wxWidgets Web site, such as:
-
-- mmedia.zip. Audio, CD, video access for Windows and Linux.
-- ogl3.zip. Object Graphics Library: build network diagrams, CASE tools etc.
-- tex2rtf3.zip. Tex2RTF: create Windows Help, HTML, and Word RTF files from
- the same document source.
General installation notes
--------------------------
After unzipping everything your directory tree should look something like
this:
-x:\wx\wxWidgets-2.7.0\docs (your HTML reference manual)
-x:\wx\wxWidgets-2.7.0\include\wx
-x:\wx\wxWidgets-2.7.0\include\wx\generic
-x:\wx\wxWidgets-2.7.0\include\wx\html
-x:\wx\wxWidgets-2.7.0\include\wx\os2
-x:\wx\wxWidgets-2.7.0\samples\.... (all the sample directories)
-x:\wx\wxWidgets-2.7.0\src
-x:\wx\wxWidgets-2.7.0\src\common
-x:\wx\wxWidgets-2.7.0\src\generic
-x:\wx\wxWidgets-2.7.0\src\html
-x:\wx\wxWidgets-2.7.0\src\jpeg
-x:\wx\wxWidgets-2.7.0\src\os2
-x:\wx\wxWidgets-2.7.0\src\png
-x:\wx\wxWidgets-2.7.0\src\tiff
-x:\wx\wxWidgets-2.7.0\src\zlib
+x:\wx\wxWidgets-2.8.0\docs (your HTML reference manual)
+x:\wx\wxWidgets-2.8.0\include\wx
+x:\wx\wxWidgets-2.8.0\include\wx\generic
+x:\wx\wxWidgets-2.8.0\include\wx\html
+x:\wx\wxWidgets-2.8.0\include\wx\os2
+x:\wx\wxWidgets-2.8.0\samples\.... (all the sample directories)
+x:\wx\wxWidgets-2.8.0\src
+x:\wx\wxWidgets-2.8.0\src\common
+x:\wx\wxWidgets-2.8.0\src\generic
+x:\wx\wxWidgets-2.8.0\src\html
+x:\wx\wxWidgets-2.8.0\src\jpeg
+x:\wx\wxWidgets-2.8.0\src\os2
+x:\wx\wxWidgets-2.8.0\src\png
+x:\wx\wxWidgets-2.8.0\src\tiff
+x:\wx\wxWidgets-2.8.0\src\zlib
If you are using VisualAge, you will also need to ensure you have a
-\lib directory as well, x:\wx\wxWidgets-2.7.0\lib
+\lib directory as well, x:\wx\wxWidgets-2.8.0\lib
and you will have to set a WXWIN environment variable in your
config.sys,
-SET WXWIN=X:\WX\WXWINDOWS-2.7.0;
+SET WXWIN=X:\WX\WXWINDOWS-2.8.0;
Compilation
-----------
Compilation with VisualAge
--------------------------
-In addition to VisualAge V3.0 Fixpack 8 you will need the following inorder
+In addition to VisualAge V3.0 Fixpack 8 you will need the following in order
to successfully build and use wxWidgets for OS/2:
1. IBM OS/2 Toolkit Version 4.5 or later
dbtable.cpp. save you changes to temp.def. Delete wx23.def and rename your
temp.def to wx23.def and you are ready to go.
-I hope to clean up the .dll builds at some point before the the library is
+I hope to clean up the .dll builds at some point before the library is
a full fledged production caliber product. Fortunately EMX and Watcom can use
the import and export pragmas successfully negating the need for manual .def
files. VA 3.0, unfortunately in C++ does not properly export the mangled
update) e.g. wxGTK or wxX11 as well.
In the following, let's assume you decided to build in
-\wx\wxWidgets-2.7.0\build\pm. Now we need to set some environment
+\wx\wxWidgets-2.8.0\build\pm. Now we need to set some environment
variables, namely MAKESHELL (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 MAKESHELL=ash
-SET INSTALL=/wx/wxWidgets-2.7.0/install-sh -c
+SET INSTALL=/wx/wxWidgets-2.8.0/install-sh -c
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.
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.
-\wxWidgets-2.7.0\build\gtk), you'll have to do a `make clean' first.
+\wxWidgets-2.8.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
OS/2 port, all of those ports work slightly better with POSIX/2's cExt
library. If include and library path include the suitable paths, -lcExt
-is automatically appended to the linker flags by the configure script.
+is automatically appended to the linker flags by the configure script.
projects / wxWidgets.git / blobdiff