COMPATIBLE_HOST

COMPATIBLE_HOST

[Moore, Thomas (FtWorth)]

I have a binary recipe that is only compatible with x86 and x86_64 systems. I *think* specifying the COMPATIBLE_HOST in my recipe would be a good idea. However, I've been unable to find any documentation, or even a good description, of this variable. Can someone help me out here?

Thanks,

Thomas

Re: COMPATIBLE_HOST

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 654 bytes --]

Hi Thomas,

On 2 February 2015 at 15:17, Moore, Thomas (FtWorth) <Thomas.Moore2@atk.com>
wrote:

> I have a binary recipe that is only compatible with x86 and x86_64
> systems. I *think* specifying the COMPATIBLE_HOST in my recipe would be a
> good idea. However, I've been unable to find any documentation, or even a
> good description, of this variable. Can someone help me out here?
>

The manual has a section in the glossary:

http://www.yoctoproject.org/docs/1.7.1/mega-manual/mega-manual.html#var-COMPATIBLE_HOST

And yes, this is the idiom.  Lots of meta-intel for example uses
COMPATIBLE_HOST = '(i.86|x86_64).*-linux'.

Ross

[-- Attachment #2: Type: text/html, Size: 1260 bytes --]

Re: COMPATIBLE_HOST

[Gary Thomas]

On 2015-02-02 08:17, Moore, Thomas (FtWorth) wrote:
> I have a binary recipe that is only compatible with x86 and x86_64 systems. I *think* specifying the COMPATIBLE_HOST in my recipe would be a good idea. However, I've been unable to find any documentation, or even a good description, of this variable. Can someone help me out here?

I think you really need to use COMPATIBLE_MACHINE instead.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: COMPATIBLE_HOST

[Moore, Thomas (FtWorth)]

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.

Thanks,

Thomas


-----Original Message-----
From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Gary Thomas
Sent: Monday, February 02, 2015 9:23 AM
To: yocto@yoctoproject.org
Subject: Re: [yocto] COMPATIBLE_HOST

On 2015-02-02 08:17, Moore, Thomas (FtWorth) wrote:
> I have a binary recipe that is only compatible with x86 and x86_64 systems. I *think* specifying the COMPATIBLE_HOST in my recipe would be a good idea. However, I've been unable to find any documentation, or even a good description, of this variable. Can someone help me out here?

I think you really need to use COMPATIBLE_MACHINE instead.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
-- 
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: COMPATIBLE_HOST

[Moore, Thomas (FtWorth)]

[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]

Ross,

Perfect. For whatever reason, the manual doesn’t come up when I google COMPATIBLE_HOST. Looks like I’ll need to bookmark the mega manual.

Thanks,

Thomas

From: Burton, Ross [mailto:ross.burton@intel.com]
Sent: Monday, February 02, 2015 9:21 AM
To: Moore, Thomas (FtWorth)
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] COMPATIBLE_HOST

Hi Thomas,

On 2 February 2015 at 15:17, Moore, Thomas (FtWorth) <Thomas.Moore2@atk.com<mailto:Thomas.Moore2@atk.com>> wrote:
I have a binary recipe that is only compatible with x86 and x86_64 systems. I *think* specifying the COMPATIBLE_HOST in my recipe would be a good idea. However, I've been unable to find any documentation, or even a good description, of this variable. Can someone help me out here?

The manual has a section in the glossary:

http://www.yoctoproject.org/docs/1.7.1/mega-manual/mega-manual.html#var-COMPATIBLE_HOST

And yes, this is the idiom.  Lots of meta-intel for example uses COMPATIBLE_HOST = '(i.86|x86_64).*-linux'.

Ross


[-- Attachment #2: Type: text/html, Size: 5071 bytes --]

Re: COMPATIBLE_HOST

[Gary Thomas]

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)'

> -----Original Message-----
> From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Gary Thomas
> Sent: Monday, February 02, 2015 9:23 AM
> To: yocto@yoctoproject.org
> Subject: Re: [yocto] COMPATIBLE_HOST
>
> On 2015-02-02 08:17, Moore, Thomas (FtWorth) wrote:
>> I have a binary recipe that is only compatible with x86 and x86_64 systems. I *think* specifying the COMPATIBLE_HOST in my recipe would be a good idea. However, I've been unable to find any documentation, or even a good description, of this variable. Can someone help me out here?
>
> I think you really need to use COMPATIBLE_MACHINE instead.
>

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: COMPATIBLE_HOST

[Richard Purdie]

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...

Cheers,

Richard

Re: COMPATIBLE_HOST

[Gary Thomas]

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
------------------------------------------------------------