From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [PATCH 04/10] meta-isar: example-module: Only disable cross-compilation for Debian kernels
Date: Mon, 5 Nov 2018 07:52:04 +0100 [thread overview]
Message-ID: <871815cb61528b97ae405bfd770869ade1084a1b.1541400730.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1541400730.git.jan.kiszka@siemens.com>
In-Reply-To: <cover.1541400730.git.jan.kiszka@siemens.com>
From: Jan Kiszka <jan.kiszka@siemens.com>
It's perfectly fine to cross-build this module with self-built kernels.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
.../recipes-kernel/example-module/example-module.bb | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/meta-isar/recipes-kernel/example-module/example-module.bb b/meta-isar/recipes-kernel/example-module/example-module.bb
index 1a4554a..996b5e2 100644
--- a/meta-isar/recipes-kernel/example-module/example-module.bb
+++ b/meta-isar/recipes-kernel/example-module/example-module.bb
@@ -7,15 +7,18 @@
include recipes-kernel/linux-module/module.inc
-SRC_URI += "file://src"
-
-S = "${WORKDIR}/src"
-
-AUTOLOAD = "${PN}"
-
# Cross-compilation is not supported for the default Debian kernels.
# For example, package with kernel headers for ARM:
# linux-headers-armmp
# has hard dependencies from linux-compiler-gcc-4.8-arm, what
# conflicts with the host binaries.
-ISAR_CROSS_COMPILE = "0"
+python() {
+ if d.getVar('KERNEL_NAME') in ['armmp', 'arm64', 'rpi-rpfv', 'amd64', '686-pae']:
+ d.setVar('ISAR_CROSS_COMPILE', '0')
+}
+
+SRC_URI += "file://src"
+
+S = "${WORKDIR}/src"
+
+AUTOLOAD = "${PN}"
--
2.16.4
next prev parent reply other threads:[~2018-11-05 6:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 6:52 [PATCH 00/10] HiKey and DE0 Nano SoC boards, further improvements and cleanups Jan Kiszka
2018-11-05 6:52 ` [PATCH 01/10] meta: builchroot: Preserve environment when calling dpkg-buildpackage Jan Kiszka
2018-11-05 9:41 ` Henning Schild
2018-11-05 9:46 ` Jan Kiszka
2018-11-05 10:05 ` Henning Schild
2018-11-05 10:16 ` [PATCH v2 " Jan Kiszka
2018-11-05 14:15 ` [PATCH " Baurzhan Ismagulov
2018-11-05 14:25 ` Jan Kiszka
2018-11-05 15:36 ` Henning Schild
2018-11-06 10:53 ` Baurzhan Ismagulov
2018-11-05 6:52 ` [PATCH 02/10] meta-isar: Remove remaining wheezy traces Jan Kiszka
2018-11-09 14:22 ` Baurzhan Ismagulov
2018-11-05 6:52 ` [PATCH 03/10] meta-isar: linux: Update mainline recipe to 4.19 Jan Kiszka
2018-11-05 6:52 ` Jan Kiszka [this message]
2018-11-05 6:52 ` [PATCH 05/10] meta-isar: Add Terasic DE0-Nano-SoC as demonstration board Jan Kiszka
2018-11-05 6:52 ` [PATCH 06/10] meta-isar: Add LeMaker HiKey board Jan Kiszka
2018-11-05 6:52 ` [PATCH 07/10] meta: linux-module: Fix arm64 cross-build Jan Kiszka
2018-11-05 6:52 ` [PATCH 08/10] wic: bootimg-efi-isar: Avoid append "None" to kernel command line Jan Kiszka
2018-11-05 6:52 ` [PATCH 09/10] wic: bootimg-efi-isar: Make agnostic to partition order Jan Kiszka
2018-11-05 6:52 ` [PATCH 10/10] image: Add install_image_deps to cache_base_repo dependencies Jan Kiszka
2018-11-06 9:59 ` [PATCH 00/10] HiKey and DE0 Nano SoC boards, further improvements and cleanups Maxim Yu. Osipov
2018-11-06 10:49 ` Baurzhan Ismagulov
2018-11-06 10:51 ` Jan Kiszka
2018-11-07 13:11 ` Maxim Yu. Osipov
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=871815cb61528b97ae405bfd770869ade1084a1b.1541400730.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.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