==================== 0: Table of contents ==================== 0: Table of contents 1: Intro 2: Using the leak checker ======== 1: Intro ======== Nautilus source tree is available from CVS (the latest-cutting edge version) and in releases (tarballs). If you plan to hack on Nautilus, please make sure you work from the CVS version. The CVS version is available on GNOME CVS. The page http://developer.gnome.org/tools/cvs.html details how to get started with GNOME CVS. If you want to contribute patches, please send mail to the nautilus maintainer (Darin Adler ) and/or the nautilus mailing list: (subscriptions should be made to with "subscribe" as a subject). Patches should be made with 'cvs diff -pu >patch' and should conform to Nautilus coding style as described in docs/style-guide.html Please read other relevant documents in the docs directory too. Please note that, while Nautilus is GPL software, the Eazel trademarks are not made available under the terms of the GPL. Specifically, you need permission to distribute the Eazel logo with CVS versions or modified versions of Nautilus. If you wish to distribute a non-released or modified version of Nautilus, please make sure to remove the eazel-logos directory from the source tree. No source code changes are necessary. Details are in the eazel-logos/LICENSE file. ========================= 2: Using the leak checker ========================= The leak checker is built as part of the eazel-tools gnome module. Build that first before you continue. Nautilus is set up to use the libleakcheck.so leak checking library. To use it, run Nautilus with LD_PRELOAD set to the path to the installed libleakcheck.so library. For example, if you are using a Bourne-compatible shell, like bash, you can run Nautilus this way to run with leak checking: LD_PRELOAD=/gnome/lib/libleakcheck.so /gnome/bin/nautilus