Patchwork [bitbake-devel,1/1] metadata: Correct "inherit" search to bbclass from oeclass

login
mail settings
Submitter Darren Hart
Date Jan. 19, 2012, 9:46 p.m.
Message ID <4a879ac75cf9be17efc7168b5ee87119e724d23c.1327009447.git.dvhart@linux.intel.com>
Download mbox | patch
Permalink /patch/19809/
State New
Headers show

Comments

Darren Hart - Jan. 19, 2012, 9:46 p.m.
Bitbake looks for bbclass now, not oeclass. Update the docs accordingly.

Signed-off-by: Darren Hart <dvhart@linux.intel.com>
---
 bitbake/doc/manual/usermanual.xml |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
Richard Purdie - Jan. 20, 2012, 4:34 p.m.
On Thu, 2012-01-19 at 13:46 -0800, Darren Hart wrote:
> Bitbake looks for bbclass now, not oeclass. Update the docs accordingly.
> 
> Signed-off-by: Darren Hart <dvhart@linux.intel.com>
> ---
>  bitbake/doc/manual/usermanual.xml |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)

Merged to master, thanks.

Richard

Patch

diff --git a/bitbake/doc/manual/usermanual.xml b/bitbake/doc/manual/usermanual.xml
index fa53ace..a677789 100644
--- a/bitbake/doc/manual/usermanual.xml
+++ b/bitbake/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>