Skip to contentSkip to conversation

metadata: Correct "inherit" search to bbclass from oeclass

PATCH Applied Darren Hart 2 participants 3 messages Jan 19, 2012 – Jan 20, 2012

lore
Share & tools
lore

Darren Hart

author
#0 lore raw

cover metadata: Correct "inherit" search to bbclass from oeclass

The following changes since commit 967de59f35acef7fb258524973473f3d154e4a37:

buildhistory_analysis: include related fields in output (2012-01-19 14:59:23 +0000)

are available in the git repository at:
git://git.pokylinux.org/poky-contrib dvhart/bitbake
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dvhart/bitbake

Darren Hart (1):
metadata: Correct "inherit" search to bbclass from oeclass

 bitbake/doc/manual/usermanual.xml |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
Signature · 1 line
1.7.6.5
author
#1 lore raw

PATCH 1/1 metadata: Correct "inherit" search to bbclass from oeclass

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

Signed-off-by Darren Hart <[email protected]>
---
 bitbake/doc/manual/usermanual.xml |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
bitbake/doc/manual/usermanual.xml +1 -1
index fa53ace..a677789 100644
@@ -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>
Signature · 1 line
1.7.6.5
Applied
#2 lore raw
Quoted 6 lines · Darren Hart

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

Signed-off-by Darren Hart <[email protected]>
---
 bitbake/doc/manual/usermanual.xml |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

Merged to master, thanks.

Richard