From: Jan Kiszka <jan.kiszka@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH] Add support for specifying package architecture using DPKG_ARCH
Date: Tue, 8 Oct 2019 13:25:28 +0200 [thread overview]
Message-ID: <b6ab8ee2-6303-2ed2-9942-5a19f518cfdd@siemens.com> (raw)
In-Reply-To: <20191007103921.77p7mjkpn3pijmhy@yssyq.m.ilbers.de>
On 07.10.19 12:39, Baurzhan Ismagulov wrote:
> Looking at dpkg-buildpackage(1), I see:
>
> -g Equivalent to --build=source,all (since dpkg 1.17.11).
>
> -G Equivalent to --build=source,any (since dpkg 1.17.11).
>
> -b Equivalent to --build=binary or --build=any,all.
>
> -B Equivalent to --build=any.
>
> -A Equivalent to --build=all.
>
> -S Equivalent to --build=source.
>
> -F Equivalent to --build=full, --build=source,binary or
> --build=source,any,all (since dpkg 1.15.8).
>
> So, the mechanism seems to be there. The question is how to split the
> processing into two steps and tell bitbake to build the "all" part once.
>
I think this boils down to removing the DISTRO_ARCH element from a
recipe PF/workdir/stamp. BUT: we will still have the issue that a source
package may build both all and some arch-specific binary packages.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-10-08 11:25 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
2019-10-07 10:20 ` Baurzhan Ismagulov
2019-10-07 10:39 ` Baurzhan Ismagulov
2019-10-08 11:25 ` Jan Kiszka [this message]
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=b6ab8ee2-6303-2ed2-9942-5a19f518cfdd@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