gecko-dev/tools
2006-06-05 20:18:27 +00:00
..
build
codesighs
debug/gdb
download-stats
downloads
dreftool
dumpdeps
elf-dynstr-gc
footprint
httptester
jprof
l10n
leaky
memory
module-deps
page-loader
performance
post_compile inital checkin of files which will eventually be a post compile step for mozilla 2006-05-17 02:21:05 +00:00
preloader
project-editor
rb
relic
reorder
reporter Fix bustage in report view 2006-06-05 20:18:27 +00:00
test-harness fix test harness bustage 2006-05-10 21:32:48 +00:00
tests
testserver
testy
tinderbox bug 335395 - [client] Correct profile detection for toolkit-based SeaMonkey, r=preed 2006-05-31 20:41:14 +00:00
trace-malloc
update-packaging
uuiddeps
wizards
cross-commit
README
trees.pl

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

* lots of other stuff (need documentation!)