Re: [PATCH v3 5/5] docs: Update custom_kernel docs for split up of kernel scripts and tools

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

On 16.08.23 16:25, Koch, Stefan (DI PA DCP R&D 3) wrote:
> On Wed, 2023-08-16 at 15:46 +0200, Jan Kiszka wrote:
>> On 16.08.23 14:14, Koch, Stefan (DI PA DCP R&D 3) wrote:
>>> Signed-off-by: Stefan Koch <stefan-koch@siemens.com>
>>> ---
>>>  doc/custom_kernel.md | 17 ++++++++++-------
>>>  1 file changed, 10 insertions(+), 7 deletions(-)
>>>
>>> diff --git a/doc/custom_kernel.md b/doc/custom_kernel.md
>>> index 73987a5b..52e03b68 100644
>>> --- a/doc/custom_kernel.md
>>> +++ b/doc/custom_kernel.md
>>> @@ -38,12 +38,17 @@ The linux-custom recipe provides support for:
>>>   7. Allow the name of the kernel image to be changed via
>>> `KERNEL_FILE` (defaults
>>>      to `vmlinuz`)
>>>  
>>> - 8. Produce a `linux-headers` package which includes kernel
>>> headers and kbuild
>>> -    scripts/tools
>>> + 8. Produce a `linux-headers` package which includes kernel
>>> headers
>>>  
>>> - 9. The `linux-headers` package shall support native and cross
>>> compiles of
>>> -    out-of-tree kernel modules. However, when built in cross-
>>> compilation mode,
>>> -    it cannot be used on the target so far.
>>> + 9. Produce a `linux-kbuild` package for both `host` and/or
>>> `target` arch
>>> +    which includes kbuild scripts and tools.
>>> +    Setting `EXTENDED_KBUILD_MODE` to `"1"` will allow using the
>>> `-compat` and
>>> +    `-native` multiarch bitbake targets at cross building to run
>>> additional
>>> +    `target` or `host` specific builds.
>>
>> Why does this need an extra control? And the semantic of that mode is
>> also by far not clear when looking at the variable name.
> 
> Variable can be dropped and turned on by default.

What would be different when building with EXTENDED_KBUILD_MODE="0"? The
kernel build be fully built for -native and -compat, right?

Jan

-- 
Siemens AG, Technology
Linux Expert Center