Re: [PATCH 0/3] linux-custom: Split up binaries from kernel headers to kbuild packages

[Jan Kiszka <jan.kiszka@siemens.com>]

On 15.11.22 14:44, Uladzimir Bely wrote:
> In mail from среда, 9 ноября 2022 г. 13:32:45 +03 user Koch, Stefan wrote:
>> Hi
>>
>> This patchset is a set of three patches:
>> - Support overwriting configured schroot dir
>> - Split up binaries from kernel headers to kbuild packages
>> - Update custom_kernel docs for split up of kernel scripts and tools
>>
> 
> Just some thoughts regarding schroot path overwriting...
> 
> What if `linux-custom` recipe could disable specific components?

Right, I sill wanted to follow up on that: Debian build profiles can do
the trick here. Define one for "host tools only", and only build that in
the second step.

> 
> I mean, currently we have this feature only for `linux-libc-dev` package, that 
> is disabled when "nolibcdev" build profile is selected. If we added similar 
> build profiles for other components, we could disable also `linux-$
> {KERNEL_NAME_PROVIDED}`, linux-image-{KERNEL_NAME_PROVIDED}, linux-headers-
> {KERNEL_NAME_PROVIDED} and `linux-image-${KERNEL_NAME_PROVIDED}-dbg`
> 
> Then, we make `linux-mainline` build all except `linux-kbuild` (if we don't 
> need cross version). And we could create the similar recipe `linux-kbuild` 
> that inherits `linux-custom`, but builds only `linux-kbuild` - with 
> ISAR_CROSS_COMPILE="0".
> 
> Of course, such an approach breaks the feature "build everything from one 
> recipe", but it doesn't require "schroot" workaround and would make build 
> process more configurable.

On top, we need a loop in the dpkg class the runs the recipe for
multiple archs, not just the target one. Then also drop that special and
ugly "-cross" package and just built the kbuild thing for the target and
the builder arch.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux