You are currently viewing a snapshot of 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, please file a bug.

checking out the source

There are two main ways for obtaining warpzilla source. Method #1 would be to retrieve directly from the cvs server the code required. Sadly, our group has not been able to commit all of the most recent changes to the os/2 source. Method #2 requires to obtain a tarball from some graciously provided ftp server.

Here are the explanations with how to go about it. For now, the ideal path will be the two methods somewhat cobbled together.

cvs access

Using your previously acquired and installed cvs tool and a bit of ingeniuity, you too can get the semi-latest version of the Warpzilla sources: check out the instructions on the source code via cvs page.

Achim has written a nice little script to do those steps for you checkout.cmd just call checkout.cmd from X:\Warpzilla.

This is a really nice little system and would be a great solution but this is the code for the mozilla classic front-end and things have been evolving at a frenetic pace: we are now mostly working on the source for nglayout and the xpfe.

Our nspr modifications have been checked in to the tip of the tree this week (November 19th) so at least that module (nsprpub) should compile straight out of the box.

cvs -z3 co NSPR
to retrieve that library,

cvs -z3 co SeaMonkeyBrowser
should get you all of the other files necessary to build the browser that are already in the cvs (without most of the OS/2 modifications yet).


We will try to supply soon a tarball of the most recent source modifications that were made but the primary aim is to get the changes into the main mozilla cvs.

A slightly convoluted directory shuffling technique was described on John Fairhurst's page but no longer seems to be available.

Joan Touzet's page of build instructions is quite complete and offers access to a recent source zipball.

So that sounds like the better solution for now.

Now, off to compilation...