summaryrefslogtreecommitdiffstats
path: root/bin/SConsDoc.py
diff options
context:
space:
mode:
authorSteven Knight <knight@baldmt.com>2005-11-17 14:23:07 (GMT)
committerSteven Knight <knight@baldmt.com>2005-11-17 14:23:07 (GMT)
commit62e2f021af43f2bd0422fabdd0b6129ae3695946 (patch)
treeb69a29b3c5e16f0b6743947b59e7084221f1e8a1 /bin/SConsDoc.py
parent9cc468f75539541734366b5e3bb9f36346ee5cda (diff)
downloadSCons-62e2f021af43f2bd0422fabdd0b6129ae3695946.zip
SCons-62e2f021af43f2bd0422fabdd0b6129ae3695946.tar.gz
SCons-62e2f021af43f2bd0422fabdd0b6129ae3695946.tar.bz2
Bring CVS back in sync.
Diffstat (limited to 'bin/SConsDoc.py')
-rw-r--r--bin/SConsDoc.py80
1 files changed, 80 insertions, 0 deletions
diff --git a/bin/SConsDoc.py b/bin/SConsDoc.py
index df28b76..57bf1d4 100644
--- a/bin/SConsDoc.py
+++ b/bin/SConsDoc.py
@@ -2,6 +2,86 @@
#
# Module for handling SCons documentation processing.
#
+
+__doc__ = """
+This module parses home-brew XML files that document various things
+in SCons. Right now, it handles Builders, construction variables,
+and Tools, but we expect it to get extended in the future.
+
+In general, you can use any DocBook tag in the input, and this module
+just adds processing various home-brew tags to try to make life a
+little easier.
+
+Builder example:
+
+ <builder name="VARIABLE">
+ <summary>
+ This is the summary description of an SCons Tool.
+ It will get placed in the man page,
+ and in the appropriate User's Guide appendix.
+ The name of any builder may be interpolated
+ anywhere in the document by specifying the
+ &b-VARIABLE;
+ element. It need not be on a line by itself.
+
+ Unlike normal XML, blank lines are significant in these
+ descriptions and serve to separate paragraphs.
+ They'll get replaced in DocBook output with appropriate tags
+ to indicate a new paragraph.
+
+ <example>
+ print "this is example code, it will be offset and indented"
+ </example>
+ </summary>
+ </builder>
+
+Construction variable example:
+
+ <cvar name="VARIABLE">
+ <summary>
+ This is the summary description of a construction variable.
+ It will get placed in the man page,
+ and in the appropriate User's Guide appendix.
+ The name of any construction variable may be interpolated
+ anywhere in the document by specifying the
+ &t-VARIABLE;
+ element. It need not be on a line by itself.
+
+ Unlike normal XML, blank lines are significant in these
+ descriptions and serve to separate paragraphs.
+ They'll get replaced in DocBook output with appropriate tags
+ to indicate a new paragraph.
+
+ <example>
+ print "this is example code, it will be offset and indented"
+ </example>
+ </summary>
+ </cvar>
+
+Tool example:
+
+ <tool name="VARIABLE">
+ <summary>
+ This is the summary description of an SCons Tool.
+ It will get placed in the man page,
+ and in the appropriate User's Guide appendix.
+ The name of any tool may be interpolated
+ anywhere in the document by specifying the
+ &t-VARIABLE;
+ element. It need not be on a line by itself.
+
+ Unlike normal XML, blank lines are significant in these
+ descriptions and serve to separate paragraphs.
+ They'll get replaced in DocBook output with appropriate tags
+ to indicate a new paragraph.
+
+ <example>
+ print "this is example code, it will be offset and indented"
+ </example>
+ </summary>
+ </tool>
+"""
+
import os.path
import imp
import sys