summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWilliam Deegan <bill@baddogconsulting.com>2023-05-17 18:57:26 -0700
committerWilliam Deegan <bill@baddogconsulting.com>2023-05-17 18:57:26 -0700
commit27132f89fa411aae71b931138561b00549a163f8 (patch)
tree4da58989f8ac461f371ec960d57d294415e205a5
parentd723812004c1e88c5bfab37b454b7164f5b4ae00 (diff)
downloadscons-git-27132f89fa411aae71b931138561b00549a163f8.tar.gz
Minor update to scanner description
-rw-r--r--doc/user/scanners.xml11
1 files changed, 7 insertions, 4 deletions
diff --git a/doc/user/scanners.xml b/doc/user/scanners.xml
index 9a0a1d34a..65389879d 100644
--- a/doc/user/scanners.xml
+++ b/doc/user/scanners.xml
@@ -149,10 +149,13 @@ over the file scanning rather than being called for each input line:
&SCons; has built-in &Scanners; that know how to look in
C/C++, Fortran, D, IDL, LaTeX, Python and SWIG source files
for information about
- other files that targets built from those files depend on -
- for example, in the case of files that use the C preprocessor,
- the <filename>.h</filename> files that are specified
- using <literal>#include</literal> lines in the source.
+ other files that targets built from those files depend on.
+
+ For example, if you have a file format which uses <literal>#include</literal>
+ to specify files which should be included into the source file
+ when it is processed, you can use an existing scanner already
+ included in &SCons;.
+
You can use the same mechanisms that &SCons; uses to create
its built-in Scanners to write Scanners of your own for file types
that &SCons; does not know how to scan "out of the box."