gecko-dev/tools
sspitzer%netscape.com 39dd050c00 fix spelling in comment. no bug #. 2001-02-01 00:29:40 +00:00
..
build
debug/gdb
dreftool
dumpdeps
elf-dynstr-gc
footprint Somewhere along the line the 5 yahoos at the beginning got removed so I'm 2001-01-23 03:04:12 +00:00
jprof fix spelling in comment. no bug #. 2001-02-01 00:29:40 +00:00
leaky
memory
performance/layout New performance data. Not part of any build. 2000-12-13 18:48:08 +00:00
post_compile Added more Intel instructions and some more debugging info. 2001-01-04 05:35:23 +00:00
project-editor
rb
tests
testserver
tinderbox Comment change only, suggestion for leak-testing a set of source code changes. 2001-01-04 02:59:30 +00:00
trace-malloc R,SR = waterson, kin, brendan. trace_malloc work. these changes should only be iuncorporated into the build process if someone defines MOZ_TRACE_MALLOC into their build 2001-01-25 22:54:05 +00:00
README
trees.pl

README

mozilla/tools
=============

This directory is for miscellaneous tools associated with mozilla.

Table of Contents
=================

* cvs.py
    A python script to checkout trees with multiple threads.
    Works on Unix and Windows. I have not tested the Mac.
    With this script, pulls can take five minutes instead of twenty.
    Of course, this script pounds the cvs server three times as hard,
    so use it with discretion.

* trees.pl (a.k.a moz)
    A perl script to navigate mozilla source trees.
    Run trees -h for usage. You will probably need to copy 'trees.pl' into
    your home directory somewhere (Just be careful to keep it up to date).
    Wrap 'trees.pl' in a shell alias called 'moz' to let you do things like,
      moz gecko webshell   - cd to webshell directory in gecko tree
      moz gecko2           - cd to same directory in gecko2 tree
      moz /                - cd to the root of the tree
      moz -o               - cd to the same subdir in the object directory


* mozilla/tools/build
    This directory is for tools that facilitate the building of the
    mozilla source code (the browser, the sdks, etc.).

* mozilla/tools/project-editor
    CGI interface to Machintosh Project Editor

* mozilla/tools/tests
    <synopsis: write me>

* mozilla/tools/tinderbox
    Scripts associated with the client-side of tinderbox.
    (scripts to checkout, build, and report the status of the tree to a
     tinderbox server.)