You are currently viewing a snapshot of www.mozilla.org taken on April 21, 2008. Most of this content is highly out of date (some pages haven't been updated since the project began in 1998) and exists for historical purposes only. If there are any pages on this archive site that you think should be added back to www.mozilla.org, please file a bug.

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

Step 3: The .mozconfig file

The .mozconfig file is a file you create in the mozilla directory that specifies options for the build. Some of the more common options are creating an obj directoy (builds objs separate from source) or enabling security (--enable-crypto) To create a .mozconfig file, see the Unix Build Configurator This is also how you turn on extensions like irc or venkman.

We strongly recommend that you build with an obj directory

Here is what our typical .mozconfig files look like for a debug build:

# sh
# Build configuration script
#
# See http://www.mozilla.org/build/unix.html for build instructions.
#

# Options for client.mk.
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/obj

# Options for 'configure' (same as command-line options).
#ac_add_options --disable-tests
#ac_add_options --enable-optimize
#ac_add_options --disable-debug
ac_add_options --enable-crypto
ac_add_options --with-extensions=all

Step 4: 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 a libs step that actually builds the code. If you encounter a situation where the export step appears to complete, but the libs step does not begin, you can type

gmake libs

to continue the build.

Step 5: Run the code

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

mozilla

to run it.