-Installing wxWindows 2.3.4
+Installing wxWidgets 2.7.0
--------------------------
-This is wxWindows 2.3.4 for IBM OS/2 Warp3 and Warp4. This is an unstable
+This is wxWidgets 2.7.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
readme.txt, notes on the Web site) carefully before mailing
wx-users or the author. Preferably, try to fix the problem first and
then send a patch to the author. Please report bugs using the
-bug report form on the wxWindows web site.
+bug report form on the wxWidgets web site.
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
+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\wxWindows-2.3.4, copy the .zip files to there and unzip them ensuring you
+C:\wx\wxWidgets-2.7.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;
+- 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++);
- PNG library source;
- ZLIB library source;
-All but the documentation is included in wxOS2-2.3.4.zip, documentation
-must be downloaded separately from the wxWindows Web site.
+All but the documentation is included in wxOS2-2.7.0.zip, documentation
+must be downloaded separately from the wxWidgets Web site.
-Other add-on packages are available from the wxWindows Web site, such as:
+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.
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\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
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\wxWidgets-2.7.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.7.0;
Compilation
-----------
--------------------------
In addition to VisualAge V3.0 Fixpack 8 you will need the following inorder
-to successfully build and use wxWindows for OS/2:
+to successfully build and use wxWidgets for OS/2:
1. IBM OS/2 Toolkit Version 4.5 or later
2. IBM TCPIP V4.0 or later
both the wx23.def and the temp.def file. Copy the header of the wx23.def to
the clipboard and paste it into the top of the temp.def file. If you have
a valid SQL database client with its SDK on your system you can skip the next
-step. wxWindows included some ODBC and SQL modules. They expect the standard
+step. wxWidgets included some ODBC and SQL modules. They expect the standard
sql.h and such to available. If you do not have a database client with its
SDK (such as DB/2) then for the .dll build you need to delete the exports for
the following three modules from your temp.def file, db.cpp, dbgrid.cpp and
the WXUSINGDLL=1 macro. For example to build the minimal sample you would
go to \samples\minimal and execute nmake all -f makefile.va WXUSINGDLL=1.
-I strongly suggest when developing apps using wxWindows for OS/2 under old
+I strongly suggest when developing apps using wxWidgets for OS/2 under old
VisualAge 3.0, that you use the dynamically linked library. The library is
very large and even the most trivial statically linked .exe can be very
large and take a long time to link. The release builds are much smaller,
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
+to compile and maintain several ports of wxWidgets 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.3.4\build\pm. Now we need to set some environment
-variables, namely MAKE_SHELL (to a Unix like shell, let's assume ash)
+\wx\wxWidgets-2.7.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 MAKE_SHELL=ash
-SET INSTALL=/wx/wxWindows-2.3.4/install-sh.
+SET MAKESHELL=ash
+SET INSTALL=/wx/wxWidgets-2.7.0/install-sh -c
-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
-and even COMSPEC to a unix like shell as well.
+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
+necessary to set SHELL or even COMSPEC to a unix like shell as well.
Now run the provided configure script by executing e.g.
`ash -c "../../configure \
- --prefix=directory_where_you_want_wxWindows_to_be_installed"'
+ --prefix=directory_where_you_want_wxWidgets_to_be_installed"'
from within the build directory (the relative path might be different
depending on the build directory you selected).
If you are already running some unix-like shell and not cmd, you may
prefer to change into the directory of a specific sample
(e.g. samples\minimal) and call make there to just build this one example.
Essentially, each sample that's not working indicates an area, where help
-in porting wxWindows to OS/2 would be appreciated.
+in porting wxWidgets to OS/2 would be appreciated.
-Finally, you can run `make install' which should install wxWindows to
+Finally, you can run `make install' which should install wxWidgets to
the desired place.
Note that we also install the wx-config script which wants to help you
compiling your own applications, e.g. `wx-config --cxxflags` will emit the
-flags that are needed for compiling source code which includes wxWindows
+flags that are needed for compiling source code which includes wxWidgets
headers, `wx-config --libs` will emit the flags needed for linking against
-wxWindows (wx-config is assuming you are calling it from a unix-like shell!).
+wxWidgets (wx-config is assuming you are calling it from a unix-like shell!).
For building a DLL, the only supported way currently is to first build the
static library and then use Andrew Zabolotny's dllar.cmd. However, this
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.
+\wxWidgets-2.7.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
projects / wxWidgets.git / blobdiff