[PATCH 0/2] Add support for per-kernel recipe variants

["chris.larson via isar-users" <isar-users@googlegroups.com>]

From: Christopher Larson <chris.larson@siemens.com>

Add support for per-kernel recipe variants. This aids in the ability for a
MACHINE to support multiple kernels, by allowing us to generate per-kernel
variants in recipes like external kernel modules.

A new variable KERNEL_NAMES will list the kernels for which variants will be
generated. It defaults to KERNEL_NAME. While this variable lists all supported
kernels for the current machine, a variant will not be generated for
KERNEL_NAME, assuming that's the recipe's baseline. Each variant listed in
KERNEL_NAMES will add kernel-<kernel_name> to the OVERRIDES variable, and
per-kernel:<kernel_name> to the BBCLASSEXTEND variable. In addition,
KERNEL_NAME will be set to the kernel name for the current variant.

In a recipe that already uses KERNEL_NAME and appends it to its PN, all you
need to do to use this is to inherit per-kernel, and add any additional kernels
you want to support to KERNEL_NAMES. The second patch in this series
does so for external kernel modules by default, but this will have no effect
on existing recipes unless KERNEL_NAMES is set to something other than
KERNEL_NAME.

Christopher Larson (2):
  per-kernel.bbclass: add class
  linux-module: inherit per-kernel

 meta/classes/per-kernel.bbclass             | 35 +++++++++++++++++++++
 meta/recipes-kernel/linux-module/module.inc |  2 +-
 2 files changed, 36 insertions(+), 1 deletion(-)
 create mode 100644 meta/classes/per-kernel.bbclass

-- 
2.47.2

-- 
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 visit https://groups.google.com/d/msgid/isar-users/20250407160148.443385-1-chris.larson%40siemens.com.