development release and OS/2 is considered to be in beta.
IMPORTANT NOTE: If you experience problems installing, please
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.
wxWindows for OS/2 requires you download various .zip files and unpack them
to your desired location on your system. Pick a location say,
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,
unzip the subdirectories as well. You will need:
- All common, generic and OS2-specific wxWindows source;
unzip the subdirectories as well. You will need:
- All common, generic and OS2-specific wxWindows source;
must be downloaded separately from the wxWindows Web site.
Other add-on packages are available from the wxWindows Web site, such as:
must be downloaded separately from the wxWindows Web site.
Other add-on packages are available from the wxWindows Web site, such as:
-x:\wx\wxWindows-2.3.3\docs (your HTML reference manual)
-x:\wx\wxWindows-2.3.3\include\wx
-x:\wx\wxWindows-2.3.3\include\wx\generic
-x:\wx\wxWindows-2.3.3\include\wx\html
-x:\wx\wxWindows-2.3.3\include\wx\os2
-x:\wx\wxWindows-2.3.3\samples\.... (all the sample directories)
-x:\wx\wxWindows-2.3.3\src
-x:\wx\wxWindows-2.3.3\src\common
-x:\wx\wxWindows-2.3.3\src\generic
-x:\wx\wxWindows-2.3.3\src\html
-x:\wx\wxWindows-2.3.3\src\jpeg
-x:\wx\wxWindows-2.3.3\src\os2
-x:\wx\wxWindows-2.3.3\src\png
-x:\wx\wxWindows-2.3.3\src\tiff
-x:\wx\wxWindows-2.3.3\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
In addition to EMX-0.9d you will need a rather complete Unix-like
environment, starting with a shell (e.g. ash) and most of the
GNU file/text/shell utilities, but also flex, bison, sed, grep, awk
In addition to EMX-0.9d you will need a rather complete Unix-like
environment, starting with a shell (e.g. ash) and most of the
GNU file/text/shell utilities, but also flex, bison, sed, grep, awk
+and GNU make. Particularly note that uname is relevant to get the
+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.
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 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
update) e.g. wxGTK or wxX11 as well.
In the following, let's assume you decided to build in
update) e.g. wxGTK or wxX11 as well.
In the following, let's assume you decided to build in
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
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.3/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
+and even COMSPEC to a unix like shell as well.
Calling `make' now should start a compile run which hopefully ends
with a library being placed in the lib subdirectory.
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
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
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.
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.
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
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