From: Gary Thomas <gary@mlbassoc.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: COMPATIBLE_HOST
Date: Mon, 02 Feb 2015 08:44:14 -0700 [thread overview]
Message-ID: <54CF9B4E.9030401@mlbassoc.com> (raw)
In-Reply-To: <1422891226.22544.4.camel@linuxfoundation.org>
On 2015-02-02 08:33, Richard Purdie wrote:
> On Mon, 2015-02-02 at 08:32 -0700, Gary Thomas wrote:
>> On 2015-02-02 08:28, Moore, Thomas (FtWorth) wrote:
>>> Gary,
>>>
>>> It seems like COMPATIBLE_MACHINE would have values such as
>> genericx86, qemux86-64, or beaglebone. If that's true, I don't think I
>> want to use COMPATIBLE_MACHINE as my recipes are only dependent on the
>> architecture.
>>
>> You can also use architecture here - basically anything that is an override can be used.
>> Similar to Ross' answer, I think this should work:
>> COMPATIBLE_MACHINE = '(i.86|x86_64)'
>
> No, that syntax is for COMPATIBLE_HOST...
So how would one write this.
We use similar syntax to specify architecture dependencies
in some ARM recipes, e.g.
COMPATIBLE_MACHINE = "ls102xa"
where ls102xa is an architecture (SOC) override and this allows
the recipe only for LS102x targets.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2015-02-02 15:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 15:17 COMPATIBLE_HOST Moore, Thomas (FtWorth)
2015-02-02 15:21 ` COMPATIBLE_HOST Burton, Ross
2015-02-02 15:31 ` COMPATIBLE_HOST Moore, Thomas (FtWorth)
2015-02-02 15:22 ` COMPATIBLE_HOST Gary Thomas
2015-02-02 15:28 ` COMPATIBLE_HOST Moore, Thomas (FtWorth)
2015-02-02 15:32 ` COMPATIBLE_HOST Gary Thomas
2015-02-02 15:33 ` COMPATIBLE_HOST Richard Purdie
2015-02-02 15:44 ` Gary Thomas [this message]
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=54CF9B4E.9030401@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=yocto@yoctoproject.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.