From patchwork Thu Jan 19 21:46:38 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [bitbake-devel, 1/1] metadata: Correct "inherit" search to bbclass from oeclass Date: Thu, 19 Jan 2012 21:46:38 -0000 From: Darren Hart X-Patchwork-Id: 19809 Message-Id: <4a879ac75cf9be17efc7168b5ee87119e724d23c.1327009447.git.dvhart@linux.intel.com> To: Richard Purdie , bitbake-devel@lists.openembedded.org Bitbake looks for bbclass now, not oeclass. Update the docs accordingly. Signed-off-by: Darren Hart --- 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 fa53ace..a677789 100644 --- a/bitbake/doc/manual/usermanual.xml +++ b/bitbake/doc/manual/usermanual.xml @@ -204,7 +204,7 @@ include directive.
Inheritance NOTE: This is only supported in .bb and .bbclass files. - The inherit 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 BBPATH, where filename is what you inherited. + The inherit 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 BBPATH, where filename is what you inherited.
Tasks