|
|
|
|
Welcome to the home of FreeBSD for newbies...
|
|
|
Once apon a time, there was a company called netscape that created a browser called Mozilla. Despite the fact that the company
spelled the name netscape, you were supposed to pronounce it Mozilla. In any case, this browser was one of the best in the world (maybe even the best), and our freinds down at netscape made it even better by turning it over to the Open Source community.
Over time, Mozilla could not only ski the web but also read e-mail, gather files using FTP, read simple programs with Java and even read Netnews all through a single graphical interface. |
|
|
|
|
|
|
|
Unix Detailed Build Instructions
This is a guide to building Mozilla on Unix
including,
- A list of the required development tools.
- Commands to build Mozilla using the Autoconf build
system.
For documentation on developing features or fixing
bugs, look at the Mozilla Technical Documents or
Mozilla
Library. For general Unix issues, look at the
Mozilla
Unix.
Your hardware should
be equal to, or better than:
- 32 MB RAM, 128 MB swap (128 MB RAM recommended)
- For debug builds: at least 1.5 GB free disk space
(2 GB recommended)
- For optimized builds: at 300 MB free disk space
(500 MB recommended)
The following software should be installed. (If you
are running Redhat 6.0 or later, you should be all set.)
- If you're using a glibc 2.07 system, you need this
patch
- egcs 1.0.3 (or higher),
or gcc 2.7.2.x (2.8.x
still has some bugs),
or your platform's native
C/C++ compiler.
egcs is recommended, this is
the compiler that the Linux tinderboxes and many
developers are using.
Redhat 7.0 Users: the
compiler distributed with RH 7.0 is buggy, and it is
recommended that you upgrade to the latest compilers
in the Rawhide distribution (2.96-77
or later): you'll need the packages named gcc-c++,
gcc, and cpp. Also pick up the latest gdb while you're
there, if you're going to be debugging mozilla.
- Perl 5.004 (or higher)
- GNU make 3.74
GNU
make 3.77 shipped with bug a that breaks the NSPR
build.
There is a known problem with parallel
builds in NSPR using GNU make 3.78-3.79.1 .
- CVS
1.10 (or higher). To get started:
setenv CVSROOT
:pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot
cvs login (password:
anonymous) (You only need
to do the login once.)
- GTK+ / GLib 1.2.0 (or
higher).
- libIDL 6.3 (or
higher).
Source snapshots are available from
Mozilla via ftp. If using the RPMs,
you'll need both the regular rpm and the -devel rpm.
- zip 2.3 (or higher)
OPTIONAL
- Autoconf 2.12 (which
requires GNU m4), is necessary if
you want to hack on configure.in. If you have no
idea what this means, then don't worry about it.
It's optional.
There are two ways to get the code:
- ftp: Drops are generally
produced at least once per month, and are known to
compile and even run on a few platforms.
- CVS: Provides the most
current code, but is slower than ftp. (First check
that Tinderbox is green to be sure
it will compile.)
setenv CVSROOT
:pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot
cvs login
(password: anonymous; you only
need to login once)
cvs co mozilla/client.mk
cd mozilla
gmake -f client.mk checkout
The makefile pulls the right source for
building mozilla, which includes some tagged branches
(e.g., NSPR).
Manually drive the build
cd mozilla
./configure
gmake
Once you have configured, you only have to run
configure if you add or remove
Makefile.in files (cvs update can do this. Beware!). The
list of makefiles is in
mozilla/allmakefiles.sh
For build system hackers: If you change configure.in,
cd to mozilla, and run autoconf.
This generates a new configure script. (When you checkin
configure.in, cvs will run autoconf and check in a new
configure script for you).
Automated build (client.mk)
- Save the script from Unix Build Configurator as
~/.mozconfig.
cvs co -f mozilla/client.mk
cd mozilla
gmake -f client.mk
If you want to build without pulling the tree (as
in, you already have the source lying around),
If you
just want to pull the tree,
gmake -f client.mk checkout
cd dist/bin and you should see
links to the scripts to run the executables:
mozilla-viewer.sh and
mozilla-apprunner.sh.
- If the scripts do not work, set
LD_LIBRARY_PATH and run
viewer and apprunner
directly. Set LD_LIBRARY_PATH to
include dist/bin, and the NSPR and GTK libraries. (For
example, you might set it to
.:../../nspr/lib).
- On HP-UX, the equivalent environment variable is
SHLIB_PATH.
- On AIX, the equivalent environment variable is
LIBPATH.
- If you run the executables from anywhere other
than dist/bin, you must set the environment variable
MOZILLA_FIVE_HOME to point to the
absolute path of the dist/bin directory.
- Update your tree by re-checking out the source,
e.g. repeating the initial checkout process.
- Parallel builds: just adding -j4 to gmake doesn't
work, you need to do this:
setenv MAKE gmake -j4
|
|
|
|
|
