diff options
| author | Darren Hart <dvhart@linux.intel.com> | 2012-01-19 13:46:38 -0800 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-01-20 16:47:38 +0000 |
| commit | 11cce8013797b4c1623891bd8a191fe326d33ed3 (patch) | |
| tree | f262afa2107c0ca5d3e163bf6bfe3346083dc224 /bitbake/doc | |
| parent | 0779a90e2a39a16867afb1ce0202db13f62d4f77 (diff) | |
| download | poky-11cce8013797b4c1623891bd8a191fe326d33ed3.tar.gz | |
usermanual: Correct "inherit" search to bbclass from oeclass
Bitbake looks for bbclass now, not oeclass. Update the docs accordingly.
(Bitbake rev: 8b713708541f85a4252c0f7b683aff4407c7d3e0)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/doc')
| -rw-r--r-- | bitbake/doc/manual/usermanual.xml | 2 |
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> |