From 24f1745c5b85c99d24a6b43a2e348af81ae1ca09 Mon Sep 17 00:00:00 2001
From: Graham Percival <graham@percival-music.ca>
Date: Fri, 4 Mar 2011 12:16:28 +0000
Subject: [PATCH] CG: add tips for build system work.

---
 Documentation/contributor/build-notes.itexi | 27 +++++++++++++++++++++
 1 file changed, 27 insertions(+)

diff --git a/Documentation/contributor/build-notes.itexi b/Documentation/contributor/build-notes.itexi
index 1cd849be2e..a4974fd9bc 100644
--- a/Documentation/contributor/build-notes.itexi
+++ b/Documentation/contributor/build-notes.itexi
@@ -10,6 +10,7 @@ chapter.}
 
 @menu
 * Build system overview::
+* Tips for working on the build system::
 * Doc build::
 * Website build::
 @end menu
@@ -55,6 +56,32 @@ myself of this.  The "end result" is just a series of command-line
 commands.  All the black magick is just an attempt to construct
 those commands.
 
+@node Tips for working on the build system
+@section Tips for working on the build system
+
+@itemize
+@item
+Add:
+
+@example
+echo "aaa"
+
+echo "bbb"
+@end example
+
+to the build system files in various places.  This will let you
+track where the program is, in various points of the build.
+
+@item
+First task: understand how @code{make website} works,
+@emph{without} the translations.  Looking at the english-only
+website is the best introduction to the build system... it only
+covers about 5% of the whole thing, but even that will likely take
+10 hours or more.
+
+@end itemize
+
+
 
 @node Doc build
 @section Doc build
-- 
2.39.5