[Openembedded-architecture] Yocto Compatible 2.0 + signature changes

[Patrick Ohly]

On Thu, 2017-05-11 at 08:54 +0200, Patrick Ohly wrote:
> I've come up with a more general approach that might be worth
> exploring
> further:
>       * copy the .bbappend content into a .bbclass
>       * in the .bbappend: inherit
>         ${@bb.utils.contains('DISTRO_FEATURES', 'foo',
>         'bar-my-former-bbappend', d)}
> 
> The downside is that these pseudo-classes clutter the "classes"
> directory. A natural place would be to put the .bbclass alongside
> the .bbappend file, but that doesn't work, and the failure shows that
> classes really are expected in a "classes" directory relative to the
> BBFILES:

s/BBFILES/BBPATH/

I've experimented further and found that one can put the pseudo .bbclass
into a recipe's "classes" directory, without even changing BBPATH. I'm
not entirely sure why it works, though, as BBPATH has no entry for the
"current" directory.

So it seems that this approach already works reasonably well, albeit
with slightly misleading statements and file names (inherit instead of
require/include, .bbclass suffix instead of .inc, extra "classes"
directory).

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.