From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Amend recipes which do not contain a (new) target machine in COMPATIBLE_MACHINE
Date: Wed, 08 Jun 2011 13:55:43 +0200 [thread overview]
Message-ID: <isnnvv$n8f$1@dough.gmane.org> (raw)
In-Reply-To: <0C757E680E33864AB113392C7E83F910BE5183@GSX300A.mxchg.m.corp>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08-06-11 13:44, Hauser, Wolfgang (external) wrote:
> Hello,
>
> I added a new machine definition for our hardware (hardware is almost
> like beagleboard xM) and want to add the specific patches and
> configurations by using the amend class in my additional layer.
>
> If I amend the kernel recipe (linux-omap-psp_2.6.32.bb) for machines
> contained in COMPATIBLE_MACHINE, the amend.inc is found and my
> amendments are done well (for omap3evm and beagleboard).
>
> If I want to build the kernel for my machine, the kernel recipe
> linux-omap-psp_2.6.32.bb was skipped in case of not containing my new
> machine in COMPATIBLE_MACHINE and the wrong kernel is build.
>
> I need only a view additions to the linux-omap-psp-2.6.32 kernel so I
> don't want to copy the original recipe into my layer and change it. I
> have to build my system for omap3evm, beagleboard and our specific
> hardware.
>
> Is there a possibility to avoid the skipping of the kernel recipe for a
> machine not contained in COMPATIBLE_MACHINE ? Or add the machine for
> amending somewhere ?
Stupid question: why not send patches to add your machine to OE?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFN72M/MkyGM64RGpERAhLTAJ9qHNv0eInsZR/TlEroTi9tEV2aawCfdVJg
OpHnn2F0ulVD9E8Jh6fPMDc=
=S3P7
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-06-08 11:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 11:44 Amend recipes which do not contain a (new) target machine in COMPATIBLE_MACHINE Hauser, Wolfgang (external)
2011-06-08 11:55 ` Koen Kooi [this message]
2011-06-08 12:02 ` Hauser, Wolfgang (external)
2011-06-08 12:01 ` Phil Blundell
2011-06-08 12:17 ` Hauser, Wolfgang (external)
2011-06-08 12:21 ` Phil Blundell
2011-06-08 15:46 ` Hauser, Wolfgang (external)
2011-06-08 15:52 ` Denys Dmytriyenko
2011-06-08 16:10 ` Hauser, Wolfgang (external)
2011-06-08 15:54 ` Phil Blundell
2011-06-08 16:00 ` Koen Kooi
2011-06-08 16:13 ` Hauser, Wolfgang (external)
2011-06-08 16:50 ` Stefan Schmidt
2011-06-08 17:02 ` Hauser, Wolfgang (external)
2011-06-08 17:21 ` Stefan Schmidt
2011-06-08 19:34 ` Koen Kooi
2011-06-09 9:42 ` Hauser, Wolfgang (external)
2011-06-09 12:03 ` Stefan Schmidt
2011-06-09 22:36 ` Khem Raj
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='isnnvv$n8f$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-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.