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.

Important: The GCC build is not working at this time.

Warpzilla Build Instructions Part Two - Build The Lizard (10/07/2002)

VisualAge only

For VisualAge only, you need to tweak some compiler headers and some toolkit headers.

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 */

VisualAge and GCC

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

In the PERLLIB/LIB directory, edit the file FindBin.pm. Search for the line:

 if ($^O eq 'MSWin32')

Change it to:

 if (($^O eq 'MSWin32') || ($^O eq 'os2'))

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 (if applicable)
MOZTOOLS

Note: that if you have all of your tools directory of off the root directory of the same drive from which you run SETMOZENV.CMD, you do not need to set these variables.

Once you have set the necessary variables, type:

SETMOZENV

for a VisualAge build or

SETMOZENV gcc

for a GCC build.

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 directory which separates the source code from the built code or enabling security. To create a .mozconfig file, see the Unix Build Configurator

We strongly recommend that you build with an obj directory

Here is what our typical .mozconfig file 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
ac_add_options --disable-profilesharing

Step 4: Build the code

Go to the mozilla directory and type:

gmake -f client.mk build

Step 5: Run the code

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

mozilla

to run it.

Mozilla