From: git@git.openembedded.org
To: bitbake-devel@lists.openembedded.org
Subject: Darren Hart : usermanual: Correct "inherit" search to bbclass from oeclass
Date: Fri, 20 Jan 2012 16:43:39 +0000 (UTC) [thread overview]
Message-ID: <20120120164339.3588E10334@opal> (raw)
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(-)
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>
reply other threads:[~2012-01-20 16:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120120164339.3588E10334@opal \
--to=git@git.openembedded.org \
--cc=bitbake-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.