Re: [PATCH v6 3/5] linux-custom: Provide target and host specific kernel kbuild packages

["'Koch, Stefan' via isar-users" <isar-users@googlegroups.com>]

On Thu, 2024-07-04 at 13:02 +0000, Hombourger, Cedric (DI CTO FDS CES
LX) wrote:
>
>
> > ________________________________________
> > From: Koch, Stefan (DI PA DCP R&D 3) <stefan-koch@siemens.com>
> > Sent: Thursday, July 4, 2024 2:44 PM
> > To: amikan@ilbers.de <amikan@ilbers.de>;
> > isar-users@googlegroups.com <isar-users@googlegroups.com>
> > Cc: Storm, Christian (T CED OES-DE) <christian.storm@siemens.com>;
> > ibr@ilbers.de <ibr@ilbers.de>; Hombourger, Cedric (DI CTO FDS CES
> > LX) > <cedric.hombourger@siemens.com>; Adler, Michael (T CED OES-
> > DE) <michael.adler@siemens.com>; Sudler, Simon (DI PA DCP TI)
> > <simon.sudler@siemens.com>; Moessbauer, Felix (T CED OES-DE)
> > <felix.moessbauer@siemens.com>; Schmidt, Adriaan (T CED EDC-DE)
> > <adriaan.schmidt@siemens.com>; Kiszka, Jan (T CED)
> > <jan.kiszka@siemens.com>; ubely@ilbers.de <ubely@ilbers.de>
> > Subject: Re: [PATCH v6 3/5] linux-custom: Provide target and host
> > specific kernel kbuild packages
> >
> > On Thu, 2024-07-04 at 09:12 +0300, Anton Mikanovich wrote:
> > > 14/02/2024 12:10, 'Stefan Koch' via isar-users wrote:
> > > > When using a cross build this patch does introduce
> > > > target and host specific kernel kbuild packages that
> > > > ship the "scripts" and "tools" binaries.
> > > >
> > > > The "-kbuildtarget" and "-native" multiarch bitbake targets are
> > > > useable to run
> > > > additional target or host specific builds for kbuild scripts
> > > > and
> > > > tools.
> > > >
> > > > Using the "-kbuildtarget" bitbake target enables the build of
> > > > a target specific kbuild package at cross builds.
> > > > So using "linux-kbuild" provides the package for the target
> > > > platform.
> > > >
> > > > Using the "-native" bitbake target enables the build of
> > > > a host specific kbuild package at cross builds.
> > > > When cross building using "linux-kbuild-native"
> > > > provides the package for the host platform.
> > > >
> > > > Only the "host" specific package is built automatically at
> > > > cross
> > > > builds.
> > > >
> > > > This solves this from doc/custom_kernel.inc:
> > > > - The kernel headers package has not supported both native
> > > >    and cross compilation of kernel modules when itself was
> > > > cross
> > > > built
> > > > - Future roadmap: Generate kernel headers package for both host
> > > > and target when using a cross build
> > > >
> > > > Signed-off-by: Stefan Koch <stefan-koch@siemens.com>
> > >
> > Hello Stefan,
> > >
> > > The changes from this patch probably cause wrong asm headers
> > > placing:
> > >
> > > https://github.com/ilbers/isar/issues/105
> > >
> > > Can you please take a look?
> > Thanks. I have created two patches. I'll send these to the list.
> > KERNEL_LIBC_DEV_DEPLOY must set manually to 1 otherwise build is
> > skipped and linux-libc-dev binary package from debian is used.
Sent both to the list...
>
> Should we switch to always generate this package but with a suffix (-
> ${KERNEL_NAME}) and add the following to its package spec:
> Provides: linux-libc-dev
> Replaces: linux-libc-dev
> Conflicts: linux-libc-dev
>
> I have been recently experimenting with this change. This allows both
> Debian's linux-libc-dev and a custom linux-libc-dev package to co-
> exist in a package repository. People wanting their custom linux-
> libc-headers in the sbuild environment (e.g. because they have a
> driver shipping custom headers with additional ioctls defined) to get
> them installed there.

Seems to be make sense. Might be renaming from:
linux-libc-dev
linux-libc-dev-${DISTRO_ARCH}-cross

to:
linux-libc-dev-${KERNEL_NAME_PROVIDED}
linux-libc-dev-${KERNEL_NAME_PROVIDED}-${DISTRO_ARCH}-cross
>
> I am happy to send a PATCH if people are OK with the approach. That
> patch would let us mark KERNEL_LIBC_DEV_DEPLOY as deprecated and
> eventually remove it in a not too distant future
Will you include that change above, too?
>
> Cedric

--
Stefan Koch
Siemens AG
http://www.siemens.com/

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/b11015b69f4c68b194bde2f00a7edcf9b1bba543.camel%40siemens.com.