From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Dalamagkidis,
Konstantinos" <konstantinos.dalamagkidis@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH] Add support for specifying package architecture using DPKG_ARCH
Date: Mon, 30 Sep 2019 08:07:25 +0200 [thread overview]
Message-ID: <6c7eeaaa-5f26-0836-e80e-e130d1f54347@siemens.com> (raw)
In-Reply-To: <20190911084104.19625-1-konstantinos.dalamagkidis@siemens.com>
On 11.09.19 10:41, [ext] Dalamagkidis, Konstantinos wrote:
> For some packages we want to be able to specify the "all" architecture.
>
> Signed-off-by: Konstantinos Dalamagkidis <konstantinos.dalamagkidis@siemens.com>
> ---
> meta/classes/debianize.bbclass | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/meta/classes/debianize.bbclass b/meta/classes/debianize.bbclass
> index ad3a98e..c231b41 100644
> --- a/meta/classes/debianize.bbclass
> +++ b/meta/classes/debianize.bbclass
> @@ -4,6 +4,7 @@
> # SPDX-License-Identifier: MIT
>
> CHANGELOG_V ?= "${PV}"
> +DPKG_ARCH ??= "any"
>
> deb_add_changelog() {
> timestamp=$(find ${S}/ -type f -not -path "${S}/debian/*" -printf "%T@\n"|sort -n -r|head -n 1)
> @@ -40,7 +41,7 @@ Maintainer: ${MAINTAINER}
> Build-Depends: debhelper (>= ${compat})
>
> Package: ${PN}
> -Architecture: any
> +Architecture: ${DPKG_ARCH}
> Depends: ${DEBIAN_DEPENDS}
> Description: ${DESCRIPTION}
> EOF
>
Thinking about this again: I guess we need more to enable "all" packages
cleanly. Currently, we will build them multiple times, namely once per
DISTRO/DISTRO_ARCH, rather than just one per DISTRO.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-09-30 6:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 8:41 Dalamagkidis, Konstantinos
2019-09-30 6:07 ` Jan Kiszka [this message]
2019-10-07 10:20 ` Baurzhan Ismagulov
2019-10-07 10:39 ` Baurzhan Ismagulov
2019-10-08 11:25 ` Jan Kiszka
2019-10-07 10:21 ` Baurzhan Ismagulov
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=6c7eeaaa-5f26-0836-e80e-e130d1f54347@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=konstantinos.dalamagkidis@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