[Openembedded-architecture] Recipe Specific Sysroots

[Andreas Müller]

On Wed, Dec 7, 2016 at 5:09 PM, Andreas Müller
<schnitzeltony at googlemail.com> wrote:
> On Wed, Dec 7, 2016 at 4:21 PM, Richard Purdie
> <richard.purdie at linuxfoundation.org> wrote:
>> On Thu, 2016-12-01 at 17:32 +0100, Andreas Müller wrote:
>>> I haven't looked into implementation details but appreciate the
>>> efforts on this. Getting DEPENDS right can turn to a random
>>> iteration.
>>>
>>> One question: You might remember that I still (really) like using
>>> sysroot for quick remote debugging (have created a dirty helper [1]
>>> after gdb's source code pointers moved): Will there be a place with
>>> whole sysroot - maybe set by an option?
>>>
>>> [1] https://github.com/schnitzeltony/meta-misc/blob/master/classes/in
>>> stant-remote.bbclass
>>
>> Basically, no, there won't, at least not out the box.
> Yes - I did not expect
>>
>> 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...
>>
>> So it will change things but it should be possible to get what you need
>> one way or another.
>>
>> Cheers,
>>
>> Richard
>>
> 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?
>
Partial answer: This won't work for plugins...

Andreas