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

Changed version to 2.4.2

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_2_4_BRANCH@23581 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Julian Smart
2003-09-14 19:22:35 +00:00
parent e59fcce8b5
commit 7e6e96f608
40 changed files with 83 additions and 83 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/base/readme.txt
View File

@@ -126,6 +126,6 @@ namely:
Vadim Zeitlin
This file is accurate for the version 2.4.1 of wxBase. It was last modified on
This file is accurate for the version 2.4.2 of wxBase. It was last modified on
June 13, 2003.

2
docs/gtk/install.txt
View File

@@ -44,7 +44,7 @@ If you want to remove wxWindows on Unix you can do this:
* The GTK+ 2 case
-----------------
wxGTK 2.4.1 has support for the new version 2.0.X of GTK+. This means
wxGTK 2.4.2 has support for the new version 2.0.X of GTK+. This means
that wxGTK apps can now make use Unicode as the underlying encoding
for all text operations. This is a very fundamental change and will
need time to stabilize, so be careful. Anyways, after installing a

4
docs/latex/wx/manual.tex
View File

@@ -26,13 +26,13 @@
%\special{!/@scaleunit 1 def}
\parskip=10pt
\parindent=0pt
\title{wxWindows 2.4.1: A portable C++ and Python GUI toolkit}
\title{wxWindows 2.4.2: A portable C++ and Python GUI toolkit}
\winhelponly{\author{by Julian Smart et al
%\winhelponly{\\$$\image{1cm;0cm}{wxwin.wmf}$$}
}}
\winhelpignore{\author{Julian Smart, Robert Roebling, Vadim Zeitlin,
Robin Dunn, et al}
\date{June 2003}
\date{September 2003}
}
\makeindex
\begin{document}

2
docs/mgl/install.txt
View File

@@ -11,7 +11,7 @@ IMPORTANT NOTE:
When sending bug reports tell us what version of wxWindows you are
using (including the beta) and what compiler on what system. One
example: wxMGL 2.4.1, gcc 2.95.3, Redhat 7.0
example: wxMGL 2.4.2, gcc 2.95.3, Redhat 7.0
First steps
-----------

2
docs/motif/install.txt
View File

@@ -11,7 +11,7 @@ IMPORTANT NOTE:
When sending bug reports tell us what version of wxWindows you are
using (including the beta) and what compiler on what system. One
example: wxMotif 2.4.1, gcc 2.95.4, Redhat 6.1
example: wxMotif 2.4.2, gcc 2.95.4, Redhat 6.1
First steps
-----------

4
docs/motif/readme.txt
View File

@@ -1,7 +1,7 @@
Welcome to wxWindows/Motif 2.4.1
Welcome to wxWindows/Motif 2.4.2
You have downloaded version 2.4.1 of the Motif port of
You have downloaded version 2.4.2 of the Motif port of
the wxWindows GUI library.
More information about the wxWindows project as a whole

6
docs/msw/install.txt
View File

@@ -1,8 +1,8 @@
Installing wxWindows 2.4.1
Installing wxWindows 2.4.2
--------------------------
This is wxWindows 2.4.1 for Microsoft Windows 9x/ME, Windows NT,
This is wxWindows 2.4.2 for Microsoft Windows 9x/ME, Windows NT,
Windows 2000 and Windows XP. This is an official release.
Please note that the library naming conventions for VC++
@@ -440,7 +440,7 @@ Metrowerks CodeWarrior compilation
----------------------------------
1. CodeWarrior Pro7 project files in XML format are already
included in wxMSW-2.4.1.zip and the setup version.
included in wxMSW-2.4.2.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
what you want. If you aren't sure, leave it alone and go with the

56
docs/os2/install.txt
View File

@@ -1,7 +1,7 @@
Installing wxWindows 2.4.1
Installing wxWindows 2.4.2
--------------------------
This is wxWindows 2.4.1 for IBM OS/2 Warp3 and Warp4. This is an unstable
This is wxWindows 2.4.2 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.4.1, copy the .zip files to there and unzip them ensuring you
C:\wx\wxWindows-2.4.2, 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.4.1.zip, documentation
All but the documentation is included in wxOS2-2.4.2.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.4.1\docs (your HTML reference manual)
x:\wx\wxWindows-2.4.1\include\wx
x:\wx\wxWindows-2.4.1\include\wx\generic
x:\wx\wxWindows-2.4.1\include\wx\html
x:\wx\wxWindows-2.4.1\include\wx\os2
x:\wx\wxWindows-2.4.1\samples\.... (all the sample directories)
x:\wx\wxWindows-2.4.1\src
x:\wx\wxWindows-2.4.1\src\common
x:\wx\wxWindows-2.4.1\src\generic
x:\wx\wxWindows-2.4.1\src\html
x:\wx\wxWindows-2.4.1\src\jpeg
x:\wx\wxWindows-2.4.1\src\os2
x:\wx\wxWindows-2.4.1\src\png
x:\wx\wxWindows-2.4.1\src\tiff
x:\wx\wxWindows-2.4.1\src\zlib
x:\wx\wxWindows-2.4.2\docs (your HTML reference manual)
x:\wx\wxWindows-2.4.2\include\wx
x:\wx\wxWindows-2.4.2\include\wx\generic
x:\wx\wxWindows-2.4.2\include\wx\html
x:\wx\wxWindows-2.4.2\include\wx\os2
x:\wx\wxWindows-2.4.2\samples\.... (all the sample directories)
x:\wx\wxWindows-2.4.2\src
x:\wx\wxWindows-2.4.2\src\common
x:\wx\wxWindows-2.4.2\src\generic
x:\wx\wxWindows-2.4.2\src\html
x:\wx\wxWindows-2.4.2\src\jpeg
x:\wx\wxWindows-2.4.2\src\os2
x:\wx\wxWindows-2.4.2\src\png
x:\wx\wxWindows-2.4.2\src\tiff
x:\wx\wxWindows-2.4.2\src\zlib
If you are using VisualAge, you will also need to ensure you have a
\lib directory as well, x:\wx\wxWindows-2.4.1\lib
\lib directory as well, x:\wx\wxWindows-2.4.2\lib
and you will have to set a WXWIN environment variable in your
config.sys,
SET WXWIN=X:\WX\WXWINDOWS-2.4.1;
SET WXWIN=X:\WX\WXWINDOWS-2.4.2;
Compilation
-----------
@@ -168,12 +168,12 @@ 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.
If you donwloaded wxAll-2.4.1, the directories will contain unix versions
If you donwloaded wxAll-2.4.2, 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.1\docs\os2\os2-specific.zip.
For this purpose change into the top level directory (\wx\wxWindows-2.4.1)
versions contained in e.g. \wx\wxWindows-2.4.2\docs\os2\os2-specific.zip.
For this purpose change into the top level directory (\wx\wxWindows-2.4.2)
and call "unzip docs\os2\os2-specific.zip" (assuming you have InfoZip's
unzip installed). Of course, replace \wx\wxWindows-2.4.1 by the path you
unzip installed). Of course, replace \wx\wxWindows-2.4.2 by the path you
did choose.
Once you are done with those preliminaries, the first thing to do is to
@@ -185,13 +185,13 @@ 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.1\build\pm. Now we need to set some environment
\wx\wxWindows-2.4.2\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.4.1/install-sh.
SET INSTALL=/wx/wxWindows-2.4.2/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
@@ -245,7 +245,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.4.1\build\gtk), you'll have to do a `make clean' first.
\wxWindows-2.4.2\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

4
docs/publicity/announce.txt
View File

@@ -1,8 +1,8 @@
Announcing wxWindows 2.4.1: a cross-platform GUI toolkit
Announcing wxWindows 2.4.2: a cross-platform GUI toolkit
----------------------------------------------------------------
June 13th, 2003 -- the wxWindows team is pleased to announce
an official 2.4.1 release of the mature cross-platform C++
an official 2.4.2 release of the mature cross-platform C++
application framework.
The following platforms are supported:

2
docs/readme.txt
View File

@@ -1,4 +1,4 @@
wxWindows 2.4.1
wxWindows 2.4.2
---------------
Welcome to wxWindows, a sophisticated cross-platform C++

2
docs/x11/install.txt
View File

@@ -11,7 +11,7 @@ IMPORTANT NOTE:
When sending bug reports tell us what version of wxWindows you are
using (including the beta) and what compiler on what system. One
example: wxX11 2.4.1, gcc 2.95.4, Redhat 6.2
example: wxX11 2.4.2, gcc 2.95.4, Redhat 6.2
First steps
-----------

4
docs/x11/readme.txt
View File

@@ -1,7 +1,7 @@
Welcome to wxWindows/X11 2.4.1
Welcome to wxWindows/X11 2.4.2
You have downloaded version 2.4.1 of the X11 port of
You have downloaded version 2.4.2 of the X11 port of
the wxWindows GUI library. This runs on X11 with no
Motif, Xt, GTK+ or any other standard widget set --
instead it uses the wxUniversal widgets. The intention