[oe] creating ipks for all package dependencies

[Richard Purdie]

On Fri, 2007-11-30 at 08:21 -0800, Justin Patrin wrote:
> On Nov 30, 2007 6:15 AM, Cliff Brake <cliff.brake at gmail.com> wrote:
> > I recently ran into an issue where I bitbake'd subversion.  I then
> > tried to install subversion from an ipkg feed, and ipkg complained
> > about dependencies not being available (neon, etc).  It turns out that
> > bitbake does not run the do_package_write_ipk task due to recent
> > corrections in the way dependencies are handled, so the ipks for
> > subversion dependencies where not in the feeds.  Richard suggested
> > merging a task from poky that forces all ipk files to be generated.
> > It has not been merged in OE, and to use do the following:
> >
> > bitbake <your recipe> -c buildall
> >
> > This will force ipks for all dependencies of <your recipe> to be built
> > as well as the package you are building.
> 
> This really sounds like a bug to me....why would bitbake not build the
> ipks for runtime dependencies of a package?

Its not a bug. It does depend what you define "bitbake x" to mean.

One definition is run target x's do_build task and any dependent tasks.

Another definition could be to run target x's do_build task and the
do_build tasks of any dependencies.

OE defines what "do_build" is and can therefore chose between the above
choices, it isn't a bitbake problem. Both have use cases. The second
definition breaks the first, adding a buildall task makes both use cases
possible. If you always want buildall you can set BB_DEFAULT_TASK =
"buildall" in local.conf in theory to.

So hopefully we've got the flexible solution which lets everyone do what
they want/need?

Cheers,

Richard