summaryrefslogtreecommitdiffstats
path: root/bitbake/doc/manual/usermanual.xml
diff options
context:
space:
mode:
authorRichard Purdie <richard@openedhand.com>2006-02-10 10:11:32 +0000
committerRichard Purdie <richard@openedhand.com>2006-02-10 10:11:32 +0000
commit62dc8f47b3c17cf0b1a5d4bf4f0173d5d4fb4c1a (patch)
tree947a632b694a9a6d561f0df0a768a622e1364570 /bitbake/doc/manual/usermanual.xml
parent9a262964c8b5c5a21a68d9b66ab9259b3737999f (diff)
downloadpoky-62dc8f47b3c17cf0b1a5d4bf4f0173d5d4fb4c1a.tar.gz
Update bitbake to latest bitbake svn
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@262 311d38ba-8fff-0310-9ca6-ca027cbcb966
Diffstat (limited to 'bitbake/doc/manual/usermanual.xml')
-rw-r--r--bitbake/doc/manual/usermanual.xml6
1 files changed, 6 insertions, 0 deletions
diff --git a/bitbake/doc/manual/usermanual.xml b/bitbake/doc/manual/usermanual.xml
index b96863c031..277e615100 100644
--- a/bitbake/doc/manual/usermanual.xml
+++ b/bitbake/doc/manual/usermanual.xml
@@ -139,6 +139,12 @@ will be introduced.</para>
139 <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> 139 <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>
140 </section> 140 </section>
141 <section> 141 <section>
142 <title>Requiring Inclusion</title>
143 <para>In contrast to the <literal>include</literal> directive, <literal>require</literal> will
144raise an ParseError if the to be included file can not be found. Otherwise it will behave just like the <literal>
145include</literal> directive.</para>
146 </section>
147 <section>
142 <title>Python variable expansion</title> 148 <title>Python variable expansion</title>
143 <para><screen><varname>DATE</varname> = "${@time.strftime('%Y%m%d',time.gmtime())}"</screen></para> 149 <para><screen><varname>DATE</varname> = "${@time.strftime('%Y%m%d',time.gmtime())}"</screen></para>
144 <para>This would result in the <varname>DATE</varname> variable containing today's date.</para> 150 <para>This would result in the <varname>DATE</varname> variable containing today's date.</para>