From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>,
"Schmidt, Adriaan" <adriaan.schmidt@siemens.com>,
"Koch, Stefan (MO MLT LM EN CCI 1)" <stefan-koch@siemens.com>
Subject: PREFERRED_VERSION for custom linux kernels
Date: Wed, 22 May 2024 19:27:04 +0200 [thread overview]
Message-ID: <47492fd7-1603-4055-9069-99d67c19c5ed@siemens.com> (raw)
Hi all,
with the introduction of -kbuildtarget and the relevance of -native for
custom kernel recipes, we now have a recipe API change /wrt selecting
the kernel version (PREFERRED_VERSION_linux...) in case there are
multiple. This can look ugly downstream see [1]. I'm now also doing the
same for xenomai-images, and there I thought again about deriving the
preferred version of -native and -kbuildtarget from the one set for the
base target:
PREFERRED_VERSION_linux-xenomai-3-native ?=
"${PREFERRED_VERSION_linux-xenomai-3}"
PREFERRED_VERSION_linux-xenomai-3-kbuildtarget ?=
"${PREFERRED_VERSION_linux-xenomai-3}"
And that leads to my question: Update RECIPES-API-CHANGELOG with this
information or rather set similar defaults for
PREFERRED_VERSION_linux-${KERNEL_NAME}-native/kbuildtarget, obsoleting
the pattern above? Thoughts?
Jan
[1]
https://gitlab.com/cip-project/cip-core/isar-cip-core/-/commit/52508662349362f6e97528976f28a2cbf06e9d97
--
Siemens AG, Technology
Linux Expert Center
next reply other threads:[~2024-05-22 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 17:27 Jan Kiszka [this message]
2024-05-27 11:56 ` Jan Kiszka
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=47492fd7-1603-4055-9069-99d67c19c5ed@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=isar-users@googlegroups.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