[Buildroot] [RFC v3 00/30] Add per-package staging feature

Fabio Porcedda fabio.porcedda at gmail.com
Sun Jun 28 19:34:38 UTC 2015


On Sun, Jun 28, 2015 at 8:12 PM, Thomas Petazzoni
<thomas.petazzoni at free-electrons.com> wrote:
> Hello,
>
> On Sun, 28 Jun 2015 17:33:21 +0200, Fabio Porcedda wrote:
>
>> > Good. We'll see how it looks. So now the per-package sysroot also
>> > contains the C library and kernel headers as well? It's really a
>> > complete sysroot?
>>
>> Yes, i copy the whole directory ${STAGING_DIR}, e.g.
>> output/host/usr/arm-buildroot-linux-gnueabi/sysroot
>
> Ok. When you say "whole", you say that you also "package" what the
> toolchain installs, and create a complete sysroot from scratch for each
> package being built, including for the toolchain libs/headers ?

Yes.

>> > I'm indeed fine with solving this part as a next step, however, I'd
>> > like to at least have some basic ideas of how it will be solved, to see
>> > the big picture and see if solving the big picture is doable.
>>
>> My idea is to solve it in the same way as the staging directory,
>> copying the whole "output/host" directory expect for the sysroot part
>> if it is a host package.
>> Or maybe there is better way to do it?
>
> Again, when you say "whole", you also separate in multiple host dirs
> whatever is installed by each package, and then create a custom
> host dir when each package is being built, containing only the
> dependencies that it needs?

Yes

Best regards
-- 
Fabio Porcedda



More information about the buildroot mailing list