"Best" way to determine is building for target?

"Best" way to determine is building for target?

[Slater, Joseph]

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

To change the installation for popt but not popt-native, I said

do_install_append_pn-popt {
  ...
}

which seems to work, but is there a better way, like some ${@building_for_host("yes text","no text",d)}
construct?

Joe


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

Re: "Best" way to determine is building for target?

[Richard Purdie]

On Tue, 2012-08-07 at 21:12 +0000, Slater, Joseph wrote:
> To change the installation for popt but not popt-native, I said
>  
> do_install_append_pn-popt {
>   ...
> }
>  
> which seems to work, but is there a better way, like some
> ${@building_for_host("yes text","no text",d)}
> construct?
>  

There is the new class-target override:

do_install_append_class-target {
 ...
}


(along with class-native, class-cross and class-nativesdk)

These are due to replace the virtclass-xxxx variants but we've not
gotten around to that yet. Its a relatively new addition to the system
but should be a useful one and allow some cleanup.

Cheers,

Richard

Re: "Best" way to determine is building for target?

[Paul Eggleton]

On Tuesday 07 August 2012 22:17:21 Richard Purdie wrote:
> There is the new class-target override:
> 
> do_install_append_class-target {
>  ...
> }
> 
> 
> (along with class-native, class-cross and class-nativesdk)
> 
> These are due to replace the virtclass-xxxx variants but we've not
> gotten around to that yet. Its a relatively new addition to the system
> but should be a useful one and allow some cleanup.

It's worth noting that this is only supported in current master (will be in 
the next stable release). It was added in OE-Core revision 
cf332fd9bf685f6d42b11c1f0c37b934c7f5bcbe.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre