From: Henning Schild <henning.schild@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH][FYI] dpkg-raw: Allow multiconfig build
Date: Thu, 14 Sep 2017 10:31:08 +0200 [thread overview]
Message-ID: <20170914103108.5339a155@md1em3qc> (raw)
In-Reply-To: <0d4f7101-2608-dd43-443d-516aecb54943@ilbers.de>
Am Wed, 13 Sep 2017 18:09:32 +0300
schrieb Alexander Smirnov <asmirnov@ilbers.de>:
> P.S. all the multiconfig builds have been completed, no more issues
> found.
Sweet, thanks for finding and fixing these issues. I will look into the
whole multiconfig story and test future changes on more than one config.
Henning
> On 09/13/2017 06:00 PM, Alexander Smirnov wrote:
> > Add suffixes to stamps for tasks defined in dpkg-raw class. This
> > allows to use multiconfig.
> >
> > 8<--
> >
> > If I build Isar using command:
> >
> > $ bitbake multiconfig:qemuarm-wheezy:isar-image-base
> > multiconfig:qemuarm-jessie:isar-image-base
> >
> > There will be the following stamps created:
> >
> > 1. Without this patch:
> >
> > $ ls -1 tmp/stamps
> >
> > ...
> > example-raw-0.1-r0.do_build.raspbian-jessie-armhf
> > example-raw-0.1-r0.do_deb_package_conffiles
> > example-raw-0.1-r0.do_deb_package_prepare
> > example-raw-0.1-r0.do_fetch
> > example-raw-0.1-r0.do_populate_package
> > ...
> > [example for hello package]:
> > hello-1.0-r0.do_build.debian-jessie-armhf
> > hello-1.0-r0.do_build.debian-wheezy-armhf
> > hello-1.0-r0.do_fetch
> > hello-1.0-r0.do_unpack.debian-jessie-armhf
> > hello-1.0-r0.do_unpack.debian-wheezy-armhf
> > ...
> >
> > In this case, the "example-raw" package will be processed only
> > once, so for all the other architectures bitbake will ignore tasks
> > execution.
> >
> > 2. With this patch:
> >
> > ...
> > example-raw-0.1-r0.do_build.debian-jessie-armhf
> > example-raw-0.1-r0.do_build.debian-wheezy-armhf
> > example-raw-0.1-r0.do_deb_package_conffiles.debian-jessie-armhf
> > example-raw-0.1-r0.do_deb_package_conffiles.debian-wheezy-armhf
> > example-raw-0.1-r0.do_deb_package_prepare.debian-jessie-armhf
> > example-raw-0.1-r0.do_deb_package_prepare.debian-wheezy-armhf
> > example-raw-0.1-r0.do_fetch
> > example-raw-0.1-r0.do_populate_package.debian-jessie-armhf
> > example-raw-0.1-r0.do_populate_package.debian-wheezy-armhf
> > example-raw-0.1-r0.do_unpack.debian-jessie-armhf
> > example-raw-0.1-r0.do_unpack.debian-wheezy-armhf
> > ...
> >
> > So all the new tasks added to Isar, that are distro and/or
> > architecture specific, should have suffixes in stamps.
> >
> > 8<--
> >
> > Signed-off-by: Alexander Smirnov <asmirnov@ilbers.de>
> > ---
> > meta/classes/dpkg-raw.bbclass | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/meta/classes/dpkg-raw.bbclass
> > b/meta/classes/dpkg-raw.bbclass index f9a7411..6c6a89c 100644
> > --- a/meta/classes/dpkg-raw.bbclass
> > +++ b/meta/classes/dpkg-raw.bbclass
> > @@ -14,6 +14,7 @@ do_populate_package() {
> > bbnote "Put your files for this package in ${D}"
> > }
> >
> > +do_populate_package[stamp-extra-info] = "${DISTRO}-${DISTRO_ARCH}"
> > addtask populate_package after do_unpack before
> > do_deb_package_prepare
> > # so we can put hooks etc. in there already
> > @@ -39,6 +40,7 @@ do_deb_package_prepare() {
> > done
> > }
> >
> > +do_deb_package_prepare[stamp-extra-info] =
> > "${DISTRO}-${DISTRO_ARCH}" addtask deb_package_prepare after
> > do_populate_package before do_deb_package_conffiles
> > do_deb_package_conffiles() {
> > @@ -47,6 +49,7 @@ do_deb_package_conffiles() {
> > test -s $CONFFILES || rm $CONFFILES
> > }
> >
> > +do_deb_package_conffiles[stamp-extra-info] =
> > "${DISTRO}-${DISTRO_ARCH}" addtask deb_package_conffiles after
> > do_deb_package_prepare before do_build
> > dpkg_runbuild() {
> >
>
next prev parent reply other threads:[~2017-09-14 8:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 15:58 [PATCH v2 0/6] v4 of the custom debian package Henning Schild
2017-09-12 15:58 ` [PATCH v2 1/6] meta: Move 'do_fetch' and 'do_unpack' to base-class Henning Schild
2017-09-12 15:58 ` [PATCH v2 2/6] meta/dpkg-debian: Move 'do_install' to new dpkg-base.bbclass Henning Schild
2017-09-12 15:58 ` [PATCH v2 3/6] meta/dpkg: pull out actual build command from 'do_build' Henning Schild
2017-09-13 12:44 ` Alexander Smirnov
2017-09-13 13:41 ` Henning Schild
2017-09-13 14:40 ` Claudius Heine
2017-09-13 15:27 ` Henning Schild
2017-09-12 15:58 ` [PATCH v2 4/6] meta/dpkg: Move 'do_build' and buildchroot stuff to dpkg-base.bbclass Henning Schild
2017-09-12 15:58 ` [PATCH v2 5/6] meta/dpkg: add dpkg-raw class Henning Schild
2017-09-12 15:58 ` [PATCH v2 6/6] recipes-app/example-raw: add an example on how to use dpkg-raw Henning Schild
2017-09-13 11:39 ` Andreas Reichel
2017-09-14 7:28 ` Alexander Smirnov
2017-09-14 8:11 ` Henning Schild
2017-09-13 13:13 ` Alexander Smirnov
2017-09-13 14:15 ` Henning Schild
2017-09-13 15:06 ` Alexander Smirnov
2017-09-13 15:28 ` Henning Schild
2017-09-13 15:38 ` Alexander Smirnov
2017-09-14 8:33 ` Henning Schild
2017-09-12 17:07 ` [PATCH v2 0/6] v4 of the custom debian package Henning Schild
2017-09-13 15:00 ` [PATCH][FYI] dpkg-raw: Allow multiconfig build Alexander Smirnov
2017-09-13 15:09 ` Alexander Smirnov
2017-09-14 8:31 ` Henning Schild [this message]
2017-09-14 17:18 ` [PATCH v2 0/6] v4 of the custom debian package Alexander Smirnov
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=20170914103108.5339a155@md1em3qc \
--to=henning.schild@siemens.com \
--cc=asmirnov@ilbers.de \
--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