summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorHolger Hans Peter Freyther <zecke@selfish.org>2006-01-05 20:26:12 +0000
committerHolger Hans Peter Freyther <zecke@selfish.org>2006-01-05 20:26:12 +0000
commit34d1994b9bc47b22e219e93a3e1e27fc2cba41a6 (patch)
tree82411786942a76806b803a74b5939489f6a41ed6
parentc0b889a477758d2749788b868b27a362b17aa8c9 (diff)
downloadbitbake-34d1994b9bc47b22e219e93a3e1e27fc2cba41a6.tar.gz
bitbake/doc/manual:
-Mention the new require keyword
-rw-r--r--doc/manual/usermanual.xml6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/manual/usermanual.xml b/doc/manual/usermanual.xml
index b96863c03..277e61510 100644
--- a/doc/manual/usermanual.xml
+++ b/doc/manual/usermanual.xml
@@ -139,6 +139,12 @@ will be introduced.</para>
<para>Next, there is the <literal>include</literal> directive, which causes BitBake to parse in whatever file you specify, and insert it at that location, which is not unlike <command>make</command>. However, if the path specified on the <literal>include</literal> line is a relative path, BitBake will locate the first one it can find within <envar>BBPATH</envar>.</para>
</section>
<section>
+ <title>Requiring Inclusion</title>
+ <para>In contrast to the <literal>include</literal> directive, <literal>require</literal> will
+raise an ParseError if the to be included file can not be found. Otherwise it will behave just like the <literal>
+include</literal> directive.</para>
+ </section>
+ <section>
<title>Python variable expansion</title>
<para><screen><varname>DATE</varname> = "${@time.strftime('%Y%m%d',time.gmtime())}"</screen></para>
<para>This would result in the <varname>DATE</varname> variable containing today's date.</para>