All of lore.kernel.org
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: xenomai@xenomai.org, Jan Kiszka <jan.kiszka@siemens.com>,
	Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: [xenomai-images] [PATCH 1/1] Changes to support sbuild-based Isar
Date: Mon, 13 Dec 2021 08:41:08 +0300	[thread overview]
Message-ID: <5330380.rdbgypaU67@hp> (raw)
In-Reply-To: <094d5cdf-0528-009b-28ba-0241116f3d86@siemens.com>

In mail from четверг, 9 декабря 2021 г. 12:35:16 +03 user Jan Kiszka wrote:
> On 09.12.21 08:36, Uladzimir Bely via Xenomai wrote:
> > 
> > diff --git a/recipes-xenomai/xenomai/xenomai.inc
> > b/recipes-xenomai/xenomai/xenomai.inc index 8f13767..454dd7b 100644
> > --- a/recipes-xenomai/xenomai/xenomai.inc
> > +++ b/recipes-xenomai/xenomai/xenomai.inc
> > @@ -41,7 +41,5 @@ do_prepare_build() {
> > 
> >  dpkg_runbuild_prepend() {
> >  
> >      bbplain $(printf "xenomai-%s: Building revision %.20s\n" \
> >      
> >                       ${PV} ${COMMIT})
> > 
> > -
> > -    sudo chroot --userspec=$( id -u ):$( id -g ) ${BUILDCHROOT_DIR} \
> > -        sh -c "cd ${PP}/${PPS}; scripts/bootstrap"
> > +    SBUILD_PREBUILD="cd %p; scripts/bootstrap"
> 
> Could we rather provide an abstract interface to users, not carrying
> SBUILD in its name? I'm concerned that the current will make it hard to
> switch builders in the future if we may have to.
> 
> Jan

Hello.

With current approach it doesn't look easy enough. With buildchroot, it's 
possible to do anything we want in 'dpkg_runbuild_prepend' or 'prepare_build' 
task. When the actual build is started, all preparations are here and can be 
used.

Sbuild is an isolated environment, so similar things can only be somehow 
passed to the build environment. Here we use SBUILD_PREBUILD to do it, so all 
preparations are 'postponed' until real build starts and all dependencies 
installed.

If we want to unify the approach, we have 2 possible ways:
1) use something like SBUILD_PREBUILD (we can call it BUILD_PREBUILD) - so, 
the preparations won't be done in some prebuild tasks, but they will be 
postponed (with buildchroot, too) and executed during the actual build.
2) place the stuff into debian/rules, using patches or somehow else. So, the 
preparations will be done in Debian style at the correct time.

Q:
Also, there is a question regarding 'xenomai.inc' quoted above. Why 'scripts/
bootstrap' is executed manually here, before the build? There is `bootstrap` 
make target that does exactly the same, but at the build stage.
I'm simply removing 'dpkg_runbuild_prepend()' from xenomai.inc and it is still 
working for me.

-- 
Uladzimir Bely
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov




  reply	other threads:[~2021-12-13  5:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09  7:36 [xenomai-images] [PATCH 0/1] Upcoming sbuild in Isar support Uladzimir Bely
2021-12-09  7:36 ` [xenomai-images] [PATCH 1/1] Changes to support sbuild-based Isar Uladzimir Bely
2021-12-09  9:35   ` Jan Kiszka
2021-12-13  5:41     ` Uladzimir Bely [this message]
2021-12-13  7:44       ` Jan Kiszka
2021-12-09  9:42   ` Bezdeka, Florian
2021-12-09  9:43     ` Bezdeka, Florian
2021-12-09  9:48       ` Bezdeka, Florian
2021-12-09 10:11     ` 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=5330380.rdbgypaU67@hp \
    --to=ubely@ilbers.de \
    --cc=ibr@ilbers.de \
    --cc=jan.kiszka@siemens.com \
    --cc=xenomai@xenomai.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.