summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--bitbake/doc/manual/usermanual.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/bitbake/doc/manual/usermanual.xml b/bitbake/doc/manual/usermanual.xml
index fa53ace45f..a6777892ef 100644
--- a/bitbake/doc/manual/usermanual.xml
+++ b/bitbake/doc/manual/usermanual.xml
@@ -204,7 +204,7 @@ include</literal> directive.</para>
204 <section> 204 <section>
205 <title>Inheritance</title> 205 <title>Inheritance</title>
206 <para><emphasis>NOTE:</emphasis> This is only supported in .bb and .bbclass files.</para> 206 <para><emphasis>NOTE:</emphasis> This is only supported in .bb and .bbclass files.</para>
207 <para>The <literal>inherit</literal> directive is a means of specifying what classes of functionality your .bb requires. It is a rudimentary form of inheritance. For example, you can easily abstract out the tasks involved in building a package that uses autoconf and automake, and put that into a bbclass for your packages to make use of. A given bbclass is located by searching for classes/filename.oeclass in <envar>BBPATH</envar>, where filename is what you inherited.</para> 207 <para>The <literal>inherit</literal> directive is a means of specifying what classes of functionality your .bb requires. It is a rudimentary form of inheritance. For example, you can easily abstract out the tasks involved in building a package that uses autoconf and automake, and put that into a bbclass for your packages to make use of. A given bbclass is located by searching for classes/filename.bbclass in <envar>BBPATH</envar>, where filename is what you inherited.</para>
208 </section> 208 </section>
209 <section> 209 <section>
210 <title>Tasks</title> 210 <title>Tasks</title>