recipes & kernel dependencies

recipes & kernel dependencies

[Frederic BLAIN]

Hello,

I'm quite new to bitbake but I'm facing a issues with some of my
software components that require specific kernel features to be
enabled (CONFIG_GPIO_SYSFS, ...) and that the current kernel config
does not.

Is there any way to indicate in a recipe that the component depend on
specific kernel feature ? What I'm looking for is a kind of KDEPEND
that ideally would trigger an error during the do_qa task.

Thanks for your support,

--
Frédéric
This e-mail message is intended only for the use of the intended recipient(s).
The information contained therein may be confidential or privileged,
and its disclosure or reproduction is strictly prohibited.
If you are not the intended recipient, please return it immediately to its sender 
at the above address and destroy it. 

Re: recipes & kernel dependencies

[Jeff Osier-Mixon]

Hello Frédéric

I think what you are looking for is DEPENDS and RDEPENDS, and possibly
RECOMMENDS and RRECOMMENDS. Some docs are here:

http://www.openembedded.org/wiki/Getting_started
http://www.openembedded.org/wiki/Inspect_DEPENDS
http://www.yoctoproject.org/documentation

Also, the bitbake-devel list is normally used specifically for
development of the bitbake tool, so it is not often watched as closely
for those actually using the tool. You'll probably have better luck
with the openembedded-core mailing list.

hope this helps!

On Thu, Oct 11, 2012 at 6:17 AM, Frederic BLAIN
<frederic.blain@valeo.com> wrote:
> Hello,
>
> I'm quite new to bitbake but I'm facing a issues with some of my
> software components that require specific kernel features to be
> enabled (CONFIG_GPIO_SYSFS, ...) and that the current kernel config
> does not.
>
> Is there any way to indicate in a recipe that the component depend on
> specific kernel feature ? What I'm looking for is a kind of KDEPEND
> that ideally would trigger an error during the do_qa task.
>
> Thanks for your support,
>
> --
> Frédéric
> This e-mail message is intended only for the use of the intended recipient(s).
> The information contained therein may be confidential or privileged,
> and its disclosure or reproduction is strictly prohibited.
> If you are not the intended recipient, please return it immediately to its sender
> at the above address and destroy it.
>
>
> _______________________________________________
> bitbake-devel mailing list
> bitbake-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel



-- 
Jeff Osier-Mixon http://jefro.net/blog
Yocto Project Community Manager @Intel http://yoctoproject.org