gecko-dev/tools
2007-01-04 17:06:35 +00:00
..
build
build-environment/win32 Bug 363942 - MozillaBuild needs to handle MSVC8 express + SDK, r=luser 2007-01-04 17:06:35 +00:00
codesighs Bug 106386 Correct misspellings in source code 2006-11-01 23:02:18 +00:00
debug/gdb
download-stats
downloads
dreftool Bug 331921 - Fix up some corrupt/dodgy Initial Developer lines. 2006-03-30 07:57:05 +00:00
dumpdeps
elf-dynstr-gc
footprint
httptester
jprof Bug 132071: Escape < and > (used in templates) in jprof's HTML output. Initial patch by Dave Morrison <morrison@bnl.gov>, r=dbaron 2006-12-23 18:37:39 +00:00
l10n
leaky
memory
module-deps
page-loader
patcher Bug 363108: patcher2.pl --build-tools pulls from the trunk. This is bad for a number of reasons. This is a stop-gap measure to get --build-tools working again after the cairo/svg landing and the dbus landing. patch=tfullhart. r=preed. 2006-12-09 02:47:38 +00:00
performance Bug 236613: change to MPL/LGPL/GPL tri-license. 2006-12-11 09:45:41 +00:00
post_compile Removing lowercase filename because it's identical to a properly named file 2006-12-10 23:19:34 +00:00
preloader
project-editor
rb Comment about how finding debuginfo should really work. 2006-03-24 02:27:37 +00:00
release remove independent verification from this step b=363237 r=preed 2006-12-09 02:18:52 +00:00
relic Code tidy-up; add option to print out list of initial developers. 2006-12-02 01:58:14 +00:00
reorder
reporter Small html cleanup. Spaces to tabs, etc. 2006-11-25 16:18:06 +00:00
test-harness Bug 342877 - Substantially revamp/rewrite the testing-only HTTP server used in necko unit tests, making it suitable for use in Mozilla tests which require files be stored on an HTTP server (e.g. because the test depends on certain HTTP headers being set or not set, the functionality uses HTTP, etc.) but which don't require that the server have a specified hostname. Docs, implementation, and tests (!) are in netwerk/test/httpserver/; if you have questions about using the server in unit tests or have some use case which the server could support better or doesn't support at all, CC me on the bug and I'll see how I can help. Huge (huge) thanks to biesi for the review of the huge patch. r=davel on test-harness changes, r=biesi on the server and test changes 2006-12-15 02:13:54 +00:00
tests
testserver
testy
tinderbox Add Sunbird to list of 'normal' profile directories on Mac. r=coop via IRC 2006-12-13 19:12:21 +00:00
tinderbox-configs use different filter for State line b=364652 r=nrthomas 2006-12-22 17:17:50 +00:00
trace-malloc Bug 106386 Correct misspellings in source code 2006-11-01 23:02:18 +00:00
update-packaging Bug 236613: change to MPL/LGPL/GPL tri-license. 2006-12-11 09:45:41 +00:00
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!)