[Openembedded-architecture] Recipe Specific Sysroots

[Richard Purdie]

On Wed, 2016-12-07 at 17:09 +0100, Andreas Müller wrote:
> On Wed, Dec 7, 2016 at 4:21 PM, Richard Purdie
> <richard.purdie at linuxfoundation.org> wrote:
> > It would likely be straightforward to have the code populate a
> > sysroot
> > which corresponded to the image, or "sum" all the individual recipe
> > sysroot contents into one big one which when combined with the
> > above
> > class, would give you have you have today. I'm not sure we'd want
> > to do
> > that out the box for performance reasons although it could be a
> > standalone recipe I guess.
> Sounds a bit more insane to what I am doing currently...

I think we might be talking cross purposes. If you just need the
dependencies of a specific piece of software, your existing class will
probably work as it does today. The difference is that you will only
get dependencies in the sysroot and therefore if for example switching
between applications to debug, you'd have to change sysroot.

I was talking about a way of making a complete sysroot you could use
for any application you'd build.

> > So it will change things but it should be possible to get what you
> > need one way or another.
> 
> The more I think of this, I start hoping that recipe specific sysroot
> plus sources (of all dependencies) should be enough for remote
> debugging. In case this is true: Would it be a big deal to extend
> recipe specific sysroot by source files? For performance reasons
> populating source files should only be an option set in local.conf.
> 
> What do you think?

I think it likely is possible but it will have significant performance
overhead as you're effectively duplicating a lot of the do_package work
into do_populate_sysroot at this point, to the point where you may want
to make do_populate_sysroot depend on do_package and collapse the
package splitting again :/.

Cheers,

Richard