Patchwork [bitbake-devel] Darren Hart : usermanual: Correct "inherit" search to bbclass from oeclass

login
register
mail settings
Submitter git@git.openembedded.org
Date Jan. 20, 2012, 4:43 p.m.
Message ID <20120120164339.3588E10334@opal>
Download mbox | patch
Permalink /patch/19835/
State Accepted
Commit 8b713708541f85a4252c0f7b683aff4407c7d3e0
Headers show

Comments

git@git.openembedded.org - Jan. 20, 2012, 4:43 p.m.
Module: bitbake.git
Branch: master
Commit: 8b713708541f85a4252c0f7b683aff4407c7d3e0
URL:    http://git.openembedded.org/?p=bitbake.git&a=commit;h=8b713708541f85a4252c0f7b683aff4407c7d3e0

Author: Darren Hart <dvhart@linux.intel.com>
Date:   Thu Jan 19 13:46:38 2012 -0800

usermanual: Correct "inherit" search to bbclass from oeclass

Bitbake looks for bbclass now, not oeclass. Update the docs accordingly.

Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

---

 doc/manual/usermanual.xml |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

Patch

diff --git a/doc/manual/usermanual.xml b/doc/manual/usermanual.xml
index fa53ace..a677789 100644
--- a/doc/manual/usermanual.xml
+++ b/doc/manual/usermanual.xml
@@ -204,7 +204,7 @@  include</literal> directive.</para>
             <section>
                 <title>Inheritance</title>
                 <para><emphasis>NOTE:</emphasis> This is only supported in .bb and .bbclass files.</para>
-                <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>
+                <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>
             </section>
             <section>
                 <title>Tasks</title>