public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: Adriaan Schmidt <adriaan.schmidt@siemens.com>,
	isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, stefan-koch@siemens.com
Subject: Re: [PATCH v5 0/3] kbuild follow-up
Date: Thu, 23 May 2024 09:08:19 +0300	[thread overview]
Message-ID: <2b6f1ab2-8c3f-4453-8114-a3c69e5dc498@ilbers.de> (raw)
In-Reply-To: <20240516061320.3015697-1-adriaan.schmidt@siemens.com>

16/05/2024 09:13, 'Adriaan Schmidt' via isar-users wrote:
> Ok, this is indeed a tricky one...
>
> It's based on the code from Stefan's "[PATCH] linux-module: Support
> emulated module build with cross-compiled kernel" (replacing that patch),
> and on the result of staring at dependency graphs with Jan.
> This mainly addresses corner cases of the refactored kbuild packaging
> when cross-compiling.
>
> I've tested
>
> - cross-compiled custom kernel and cross module build
> - cross-compiled custom kernel and emulated module build
> - distro kernel and emulated module build
> - distro kernel and native module build
>
> Let me know if one of your use-cases is still missing.
>
> Also including some fixups (p2-3) brought up in recent reviews on the ML.
>
> Adriaan
>
> changes since v4:
> - Added "inherit multiarch" to linux-distro, so that dummy recipe PROVIDES
>    "-native" packages in native build cases.
>
> changes since v3:
> - (almost) restored the old API, where a module recipe only depends on
>    linux-headers-*. Now it's linux-headers-*-native.
> - Removed the -native suffix from all PROVIDES and DEPENDS because
>    I realized that those are added automatically by the multiarch logic.
>    Only exception is the pseudo target used to pull in the base variant
>    (which builds the headers) into the native one (which builds the kbuild
>    tools). This still needs to be named "-native".
>
> changes since v2:
> - removed a forgotten line of testing code
>
> changes since v1:
> - always use linux-kbuild-native as build dependency, even for emulated
>    builds, because the multiarch logic will select the correct package
>
>
> Adriaan Schmidt (3):
>    module.inc: fix kbuild dependency
>    linux-custom: use to_boolean when checking ISAR_CROSS_COMPILE
>    kbuildtarget.bbclass: add missing license header
>
>   meta/recipes-kernel/linux-module/module.inc   |  2 +-
>   .../linux/classes/kbuildtarget.bbclass        |  5 ++++
>   meta/recipes-kernel/linux/linux-custom.inc    | 27 ++++++++++++-------
>   meta/recipes-kernel/linux/linux-distro.bb     |  3 +++
>   4 files changed, 27 insertions(+), 10 deletions(-)
>
Applied to next, thanks.


  parent reply	other threads:[~2024-05-23  6:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-16  6:13 Adriaan Schmidt
2024-05-16  6:13 ` [PATCH v5 1/3] module.inc: fix kbuild dependency Adriaan Schmidt
2024-05-16  6:13 ` [PATCH v5 2/3] linux-custom: use to_boolean when checking ISAR_CROSS_COMPILE Adriaan Schmidt
2024-05-16  6:13 ` [PATCH v5 3/3] kbuildtarget.bbclass: add missing license header Adriaan Schmidt
2024-05-22  6:42 ` [PATCH v5 0/3] kbuild follow-up Anton Mikanovich
2024-05-22  6:52   ` Schmidt, Adriaan
2024-05-23  6:08 ` Anton Mikanovich [this message]
2024-07-02  6:41 ` Uladzimir Bely
2024-07-02  8:10   ` Schmidt, Adriaan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2b6f1ab2-8c3f-4453-8114-a3c69e5dc498@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=adriaan.schmidt@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=stefan-koch@siemens.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox