Compiling GBM + PM Tools, OpenJPEG Codec Tools
OS/2 Platform Requirements
GBM.DLL, the GBM command line tools, GBMV, GBMV2, GBMDLG, GBMLOGO, GBMVFSA,
the regression tests, the GBM plugins for Mozilla and Lucide and the OpenJPEG
JPEG2000 encoder/decoder utilities can be built for OS/2 (and eComStation)
using the following compilers:
Additional stuff required:
- IPFCPREP (IBM Employee Written Software) for preparing the online help
of GBMV2 and GBMDLG for the IBM help compiler. It's free, get it for instance
from here.
Put it somewhere in your PATH.
- IBM Developer's Toolkit for OS/2 (tested with versions 4.5x).
If you have a license for Warp 4.5x or eComStation, you'll find it on the product CD.
- ILINK 5.0 when building with GCC.
You can get it from the Mozilla for OS/2 build page or directly from
the IBM server.
Optional tools:
- LX-Lite 1.3.3 for OS/2 to (re)compress the binaries. Get it from
Hobbes.
- Infozip ZIP for OS/2 for packaging the binaries. Get it from the
developers page.
- WarpIN 1.0.14 or higher to create an installable archive. Get it from
Netlabs.
The packaging script for WarpIN's wic.exe is available on request.
Windows Platform Requirements
GBM.DLL, the GBM command line tools, the regression tests and the
OpenJPEG JPEG2000 encoder/decoder utilities can be built for Windows
(32/64bit) using the following compilers:
- Open Watcom 1.8 (Open Source)
- Microsoft Visual C++ (Express or Professional)
The GBM plugin for Mozilla can be built for Windows (32bit only) using the
following compilers:
- Microsoft Visual C++ (Express or Professional)
Additional stuff required:
- Microsoft SDK (tested with version 7.0)
Optional tools:
- Infozip ZIP for Windows for packaging the binaries. Get it from the
developers page.
Linux Platform Requirements
libgbm.so, the GBM command line tools, the regression tests and the
OpenJPEG JPEG2000 encoder/decoder utilities can be built for Linux (32/64bit)
using the following compilers:
General Steps
Unzip the source package into an empty directory. Ensure that the listed
requirements are fulfilled. The environment for the chosen compiler must
be active in the shell to be used for compiling.
Have look at the file readme.build
in the root directory of the source archive.
It explains again how to compile.
General steps:
First set path to lxlite executable/dll compressor in make.opt
if you want to compress all EXEs and DLLs. This is only supported
for OS/2 build target. For Windows and Linux targets no changes
are required in this file.
Building with IBM Visual Age C++ 3.08:
- IBM VAC++ 3.08 must be installed and all environment variables
should be set correctly before starting nmake.
nmake /f makefile.vac_os2 (for OS/2 32 bit target)
Other supported targets: all, clean, clobber, exepack, install, package
Building with Open Watcom 1.8:
- Open Watcom must be installed and all environment variables
should be set correctly before starting wmake.
The provided makefiles are in nmake style but you can use wmake's
nmake compatibility mode.
wmake -ms -h -f makefile.wat_os2 (for OS/2 32 bit target)
wmake -ms -h -f makefile.wat_w32 (for Windows 32 bit target)
Other supported targets: all, clean, clobber, exepack, install, package
(exepack is only supported for OS/2 target)
Building with GNU C Compiler:
- GCC must be installed and all environment variables
should be set correctly before starting nmake or make. The executables
and dlls built for OS/2 need libc063.dll afterwards to run.
nmake /f makefile.gcc_os2 (for OS/2 32 bit target)
make /f makefile.gcc_linux32 (for Linux 32 bit target)
make /f makefile.gcc_linux64 (for Linux 64 bit target)
Other supported targets: all, clean, clobber, exepack, install, package
(exepack is only supported for OS/2 target)
Building with Microsoft Visual C++:
- MS VC++ must be installed and all environment variables
should be set correctly before starting nmake. You need
to prepare the environment with setenv /x86 /release
or setenv /x64 /release in order to select the right
compiler set for 32bit or 64bit./
nmake /f makefile.ms_w32 (for Windows 32 bit target)
nmake /f makefile.ms_w64 (for Windows 64 bit target)
Other supported targets: all, clean, clobber, install, package
Debug compile can be activated by specifying the parameter debug=on
to
the nmake, wmake or make call.
Notes:
- You can build all sources at once by starting nmake/wmake/make in the root directory
of the source archive.
- The created import library for GBM.DLL can be used with any other OS/2 or Windows
linker. Beware that the utility archive libraries are compiler dependent and thus can only
be linked with the compiler that created them. On Linux the created libgbm.so can directly
linked against executables.
- Cross-Compiling between OS/2 and Windows is supported with OpenWatcom.
Just ensure that both compiler targets are installed via the OpenWatcom installer.
For clobber and clean targets, please use the makefiles for the host platform you're
compiling on so that the platform specific delete commands are used properly.