From: Henning Schild <henning.schild@siemens.com>
To: Felix Moessbauer <felix.moessbauer@siemens.com>
Cc: isar-users@googlegroups.com, jan.kiszka@siemens.com
Subject: Re: [PATCH 2/2] Add support for build dependencies in linux-module
Date: Thu, 7 Jul 2022 17:57:12 +0200 [thread overview]
Message-ID: <20220707175712.3497e838@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20220707154634.3860434-2-felix.moessbauer@siemens.com>
Am Thu, 7 Jul 2022 17:46:34 +0200
schrieb Felix Moessbauer <felix.moessbauer@siemens.com>:
> This patch adds support to add additional build dependencies
> when building a linux-module by using DEBIAN_BUILD_DEPENDS.
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
> meta/recipes-kernel/linux-module/files/debian/control.tmpl | 2 +-
> meta/recipes-kernel/linux-module/module.inc | 3 ++-
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git
> a/meta/recipes-kernel/linux-module/files/debian/control.tmpl
> b/meta/recipes-kernel/linux-module/files/debian/control.tmpl index
> d3f4dfe9..67b08244 100644 ---
> a/meta/recipes-kernel/linux-module/files/debian/control.tmpl +++
> b/meta/recipes-kernel/linux-module/files/debian/control.tmpl @@ -2,7
> +2,7 @@ Source: ${PN} Section: kernel Priority: optional
> Standards-Version: 3.9.6
> -Build-Depends: ${KERNEL_HEADERS_PKG}
> +Build-Depends: ${DEBIAN_BUILD_DEPENDS}
> Maintainer: ISAR project <isar-users@googlegroups.com>
>
> Package: ${PN}
> diff --git a/meta/recipes-kernel/linux-module/module.inc
> b/meta/recipes-kernel/linux-module/module.inc index
> 97eff294..a5c4336a 100644 ---
> a/meta/recipes-kernel/linux-module/module.inc +++
> b/meta/recipes-kernel/linux-module/module.inc @@ -16,6 +16,7 @@ PN .=
> "-${KERNEL_NAME}" KERNEL_IMAGE_PKG ??= "linux-image-${KERNEL_NAME}"
> KERNEL_HEADERS_PKG ??= "linux-headers-${KERNEL_NAME}"
> DEPENDS += "${KERNEL_HEADERS_PKG}"
> +DEBIAN_BUILD_DEPENDS = "${KERNEL_HEADERS_PKG}"
>
> SRC_URI += "file://debian/"
>
> @@ -26,7 +27,7 @@ inherit dpkg
> TEMPLATE_FILES = "debian/control.tmpl \
> debian/changelog.tmpl \
> debian/rules.tmpl"
> -TEMPLATE_VARS += "KERNEL_NAME KERNEL_TYPE KERNEL_IMAGE_PKG
> KERNEL_HEADERS_PKG PN" +TEMPLATE_VARS += "KERNEL_NAME KERNEL_TYPE
> KERNEL_IMAGE_PKG KERNEL_HEADERS_PKG DEBIAN_BUILD_DEPENDS PN"
In general such lists are way easier to maintain and look at diffs as
multiline. i.e.
TEMPLATE_VARS += "\
FOO\
BAR\
BLA\
"
You want to not just add the new but likely also drop the old right?
Henning
> do_prepare_build[dirs] += "${S}"
> do_prepare_build() {
next prev parent reply other threads:[~2022-07-07 15:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 15:46 [PATCH 1/2] linux-module: create S if not existing Felix Moessbauer
2022-07-07 15:46 ` [PATCH 2/2] Add support for build dependencies in linux-module Felix Moessbauer
2022-07-07 15:57 ` Henning Schild [this message]
2022-07-07 16:00 ` Moessbauer, Felix
2022-07-14 9:17 ` Anton Mikanovich
2022-07-07 16:00 ` [PATCH 1/2] linux-module: create S if not existing Henning Schild
2022-07-07 16:54 ` Jan Kiszka
2022-07-08 14:31 ` Moessbauer, Felix
2022-07-14 8:22 ` Anton Mikanovich
2022-07-14 9:05 ` Moessbauer, Felix
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=20220707175712.3497e838@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@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