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.

Skip to main content

Build Instructions for Warpzilla with EMX/GCC/PGCC

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

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: 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. 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.