From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Adriaan Schmidt <adriaan.schmidt@siemens.com>,
Felix Moessbauer <felix.moessbauer@siemens.com>,
Uladzimir Bely <ubely@ilbers.de>,
Cedric Hombourger <cedric.hombourger@siemens.com>
Subject: [PATCH v3 7/9] meta-isar: u-boot-starfive-visionfive2: Simplify build dependencies
Date: Thu, 12 Oct 2023 07:16:43 +0200 [thread overview]
Message-ID: <3426343a47bf1a0b3f9510d57e7dc7915d878b03.1697087805.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1697087805.git.jan.kiszka@siemens.com>
From: Jan Kiszka <jan.kiszka@siemens.com>
At the risk of adding the same package twice, but apt will be resolve
that, just follow the pattern of others: :native for the build env,
without any suffix for the target.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
.../u-boot/u-boot-starfive-visionfive2_2021.10+VF2-3.0.4.bb | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/meta-isar/recipes-bsp/u-boot/u-boot-starfive-visionfive2_2021.10+VF2-3.0.4.bb b/meta-isar/recipes-bsp/u-boot/u-boot-starfive-visionfive2_2021.10+VF2-3.0.4.bb
index 455bee4a..9e1b7251 100644
--- a/meta-isar/recipes-bsp/u-boot/u-boot-starfive-visionfive2_2021.10+VF2-3.0.4.bb
+++ b/meta-isar/recipes-bsp/u-boot/u-boot-starfive-visionfive2_2021.10+VF2-3.0.4.bb
@@ -8,9 +8,7 @@ require recipes-bsp/u-boot/u-boot-custom.inc
SRC_URI += "git://github.com/starfive-tech/u-boot.git;nobranch=1;protocol=https;destsuffix=u-boot-${PV}"
SRCREV = "b6e2b0e85c774a18ae668223a6e5f7d335895243"
-DEBIAN_BUILD_DEPENDS .= ", libssl-dev:${DISTRO_ARCH}"
-# when cross compiling, we need the library on the host as well, as the signature computation is done locally
-DEBIAN_BUILD_DEPENDS .= "${@ ', libssl-dev:${HOST_ARCH}' if d.getVar('ISAR_CROSS_COMPILE') == '1' else '' }"
+DEBIAN_BUILD_DEPENDS .= ", libssl-dev, libssl-dev:native"
U_BOOT_CONFIG = "starfive_visionfive2_defconfig"
U_BOOT_BIN = "u-boot.bin"
--
2.35.3
next prev parent reply other threads:[~2023-10-12 5:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 5:16 [PATCH v3 0/9] HOST_ARCH, -native, riscv64, and all the rest Jan Kiszka
2023-10-12 5:16 ` [PATCH v3 1/9] Rename BUILD_HOST_ARCH to BUILD_ARCH Jan Kiszka
2023-10-12 5:16 ` [PATCH v3 2/9] dpkg: Drop redundant PACKAGE_ARCH initialization Jan Kiszka
2023-10-12 5:16 ` [PATCH v3 3/9] crossvars: Adjust logic to account for -native package builds in non-cross setups Jan Kiszka
2023-10-12 5:16 ` [PATCH v3 4/9] multiarch: Downgrade native dependencies when building in emulated environment Jan Kiszka
2023-10-12 5:16 ` [PATCH v3 5/9] meta-isar: jh7110-u-boot-spl-tool: Rely on native annotation Jan Kiszka
2023-10-12 5:16 ` [PATCH v3 6/9] meta-isar: jh7110-u-boot-spl-image: Fix native build Jan Kiszka
2023-10-12 5:16 ` Jan Kiszka [this message]
2023-10-12 5:16 ` [PATCH v3 8/9] linux-custom: Drop unused template variable Jan Kiszka
2023-10-12 5:16 ` [PATCH v3 9/9] Move riscv64 from sid-ports to regular sid Jan Kiszka
2023-10-13 7:59 ` [PATCH v3 0/9] HOST_ARCH, -native, riscv64, and all the rest Uladzimir Bely
2023-10-13 8:36 ` Jan Kiszka
2023-10-16 7:15 ` Uladzimir Bely
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=3426343a47bf1a0b3f9510d57e7dc7915d878b03.1697087805.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=cedric.hombourger@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=ubely@ilbers.de \
/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