-Installing wxWidgets 2.5.3
+Installing wxWidgets 2.5.4
--------------------------
-This is wxWidgets 2.5.3 for Microsoft Windows 9x/ME, Windows NT, Windows 2000
+This is wxWidgets 2.5.4 for Microsoft Windows 9x/ME, Windows NT, Windows 2000
and Windows XP. This is an unstable development release. Note that unstable in
this context doesn't mean that it crashes a lot, just that the library API may
change in backwards incompatible way during the 2.5 branch lifetime.
----------------------------------
1. CodeWarrior Pro7 project files in XML format are already
- included in wxMSW-2.5.3.zip and the setup version.
+ included in wxMSW-2.5.4.zip and the setup version.
2. Review the file include\wx\msw\setup.h (or include\wx\msw\setup0.h if
you are working from the CVS version) to make sure the settings reflect
-Installing wxWidgets 2.5.3
+Installing wxWidgets 2.5.4
--------------------------
-This is wxWidgets 2.5.3 for IBM OS/2 Warp3 and Warp4. This is an unstable
+This is wxWidgets 2.5.4 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.5.3, copy the .zip files to there and unzip them ensuring you
+C:\wx\wxWidgets-2.5.4, 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;
- PNG library source;
- ZLIB library source;
-All but the documentation is included in wxOS2-2.5.3.zip, documentation
+All but the documentation is included in wxOS2-2.5.4.zip, documentation
must be downloaded separately from the wxWidgets Web site.
Other add-on packages are available from the wxWidgets Web site, such as:
After unzipping everything your directory tree should look something like
this:
-x:\wx\wxWidgets-2.5.3\docs (your HTML reference manual)
-x:\wx\wxWidgets-2.5.3\include\wx
-x:\wx\wxWidgets-2.5.3\include\wx\generic
-x:\wx\wxWidgets-2.5.3\include\wx\html
-x:\wx\wxWidgets-2.5.3\include\wx\os2
-x:\wx\wxWidgets-2.5.3\samples\.... (all the sample directories)
-x:\wx\wxWidgets-2.5.3\src
-x:\wx\wxWidgets-2.5.3\src\common
-x:\wx\wxWidgets-2.5.3\src\generic
-x:\wx\wxWidgets-2.5.3\src\html
-x:\wx\wxWidgets-2.5.3\src\jpeg
-x:\wx\wxWidgets-2.5.3\src\os2
-x:\wx\wxWidgets-2.5.3\src\png
-x:\wx\wxWidgets-2.5.3\src\tiff
-x:\wx\wxWidgets-2.5.3\src\zlib
+x:\wx\wxWidgets-2.5.4\docs (your HTML reference manual)
+x:\wx\wxWidgets-2.5.4\include\wx
+x:\wx\wxWidgets-2.5.4\include\wx\generic
+x:\wx\wxWidgets-2.5.4\include\wx\html
+x:\wx\wxWidgets-2.5.4\include\wx\os2
+x:\wx\wxWidgets-2.5.4\samples\.... (all the sample directories)
+x:\wx\wxWidgets-2.5.4\src
+x:\wx\wxWidgets-2.5.4\src\common
+x:\wx\wxWidgets-2.5.4\src\generic
+x:\wx\wxWidgets-2.5.4\src\html
+x:\wx\wxWidgets-2.5.4\src\jpeg
+x:\wx\wxWidgets-2.5.4\src\os2
+x:\wx\wxWidgets-2.5.4\src\png
+x:\wx\wxWidgets-2.5.4\src\tiff
+x:\wx\wxWidgets-2.5.4\src\zlib
If you are using VisualAge, you will also need to ensure you have a
-\lib directory as well, x:\wx\wxWidgets-2.5.3\lib
+\lib directory as well, x:\wx\wxWidgets-2.5.4\lib
and you will have to set a WXWIN environment variable in your
config.sys,
-SET WXWIN=X:\WX\WXWINDOWS-2.5.3;
+SET WXWIN=X:\WX\WXWINDOWS-2.5.4;
Compilation
-----------
update) e.g. wxGTK or wxX11 as well.
In the following, let's assume you decided to build in
-\wx\wxWidgets-2.5.3\build\pm. Now we need to set some environment
+\wx\wxWidgets-2.5.4\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.5.3/install-sh -c
+SET INSTALL=/wx/wxWidgets-2.5.4/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.5.3\build\gtk), you'll have to do a `make clean' first.
+\wxWidgets-2.5.4\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