Build Instructions for Warpzilla with VisualAge 3.6.5

Tweak VisualAge, Toolkit, and TCP/IP - only needs to be done once

Open Ibmcxxo\include\stdlib.h in an editor. Search for "min" and add the following bold lines to the code:

#ifndef XP_OS2_VACPP
#ifndef max
#define max(a, b) (((a) > (b)) ? (a) : (b))
#endif
#ifndef min
#define min(a, b) (((a) < (b)) ? (a) : (b))
#endif
#endif /* XP_OS2_VACPP */

Open Toolkit\h\stack16\utils.h in an editor. Search for "strcasecmp" and add the following bold lines to the code:

#ifndef XP_OS2_VACPP
#define strcasecmp(x,y) strcmpi((x),(y))
#define strncasecmp(x,y,z) strnicmp(x,y,z)
#endif /* XP_OS2_VACPP */

On your boot drive, go to the tcpip/bin directory, and if you have ln.exe, rename it to ln-old.exe.

Step 1: Setup your environment

SETMOZENV.CMD uses environment variables to locate the various tools that are needed for the build. The following environment variables should be set to point to where your tools are located:

GLIB
LIBIDL
AUTOCONF
EMX
VACPP365
MOZTOOLS

Note that if you have all of your tools directory of off your root directory, you do not need to set these values. When you have set up the variables, type:

SETMOZENV vacpp

Step 2: Get the Code

To get the code from CVS, go the directory where you want to put Warpzilla and type:

cvs checkout mozilla/client.mk

Then type:

cd mozilla
gmake -f client.mk pull_all
delete configure
delete nsprpub\configure

The reason we need to delete configure and nsprpub\configure is because we need to run our local version of autoconf. You only need to delete configure the very first time you pull the code, or if you ever get a conflict in configure when executing the pull_all.

We also have another problem involving a test directory that does not build on VisualAge. At this time, we recommend you disable tests. To do this, use the Unix Build Configurator to create a .mozconfig file that disables tests. Place this in the mozilla directory.

Step 3: Build the code

Go to the mozilla directory and type:

gmake -f client.mk build_all

The build itself is actually two steps, an export step that builds required tools and copies headers into the dist, and an install step that actually builds the code. If you encounter a situation where the export step appears to complete, but the install step does not begin, you can type

gmake install

to continue the build. We are investigating why this is happening. It involves a 255 error return code from gmake.

Step 4: Run the code

The executable is located in mozilla/dist/bin. Type:

mozilla

to run it.