On 20 May 2014 22:44, wrote:
> I have a recipe that only produces dev headers (macros, constants, etc).
> Builds fine, and recipes dependent on these headers are fine as well. The
> problem is that only a dev and dbg ipkg get produced for deploy (makes
> sense, there is no device side content). B
brilliant, works like a charm.thanks,-Ezekiel
Original Message
Subject: Re: [yocto] headers only recipe
From: Paul Barker <p...@paulbarker.me.uk>
Date: Tue, May 20, 2014 3:12 pm
To: ezek...@sanborndeasis.net
Cc: Yocto discussion list <yocto@yoctoproject.org>
On 20
On 20 May 2014 22:44, wrote:
> still new to yocto/oe...
>
> I have a recipe that only produces dev headers (macros, constants, etc).
> Builds fine, and recipes dependent on these headers are fine as well. The
> problem is that only a dev and dbg ipkg get produced for deploy (makes
> sense, there
still new to yocto/oe...I have a recipe that only produces dev headers (macros, constants, etc). Builds fine, and recipes dependent on these headers are fine as well. The problem is that only a dev and dbg ipkg get produced for deploy (makes sense, there is no device side content). But then do_root
