From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Darren Hart <dvhart@linux.intel.com>
Subject: Re: [PATCH 1/1] linux-yocto-custom: Clarify usage and clear COMPATIBLE_MACHINE
Date: Tue, 07 Aug 2012 12:56:54 +0100 [thread overview]
Message-ID: <1344340614.9756.225.camel@ted> (raw)
In-Reply-To: <541bca3bf62c2747fcc16b3fb8bc9ad468f6d4cb.1344268492.git.dvhart@linux.intel.com>
On Mon, 2012-08-06 at 08:56 -0700, Darren Hart wrote:
> There has been some confusion over proper use of the linux-yocto-custom
> recipe. It is not intended to build as is from meta-skeleton. It should
> be modified via a bbappend file to provide a Linux kernel config at the
> very least.
>
> Update the commentary to make this requirement more explicit. Add some
> additional detail about how to create a bbappend file and how and when
> to modify the various variables.
>
> Clear COMPATIBLE_MACHINE so bitbake will not attempt to build the recipe
> unless the user explicitly adds there machine to the variable, which
> should encourage them to read the recipe comments before attempting to
> build it.
>
> Signed-off-by: Darren Hart <dvhart@linux.intel.com>
> CC: Bruce Ashfield <bruce.ashfield@windriver.com>
> CC: Tom Zanussi <tom.zanussi@intel.com>
> Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Merged to master, thanks.
Richard
next prev parent reply other threads:[~2012-08-07 12:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 15:56 [PATCH V2 0/1] linux-yocto-custom: Clarify usage and clear COMPATIBLE_MACHINE Darren Hart
2012-08-06 15:56 ` [PATCH 1/1] " Darren Hart
2012-08-07 11:56 ` Richard Purdie [this message]
2012-08-07 3:53 ` [PATCH V2 0/1] " Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2012-08-03 23:29 [PATCH " Darren Hart
2012-08-03 23:29 ` [PATCH 1/1] " Darren Hart
2012-08-04 0:27 ` Bruce Ashfield
2012-08-06 15:52 ` Darren Hart
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=1344340614.9756.225.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox