From: Jan Kiszka <jan.kiszka@siemens.com>
To: Cedric Hombourger <Cedric_Hombourger@mentor.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH 0/1] update bitbake to version 1.44.0
Date: Fri, 8 Nov 2019 09:05:00 +0100 [thread overview]
Message-ID: <098e5cae-bd87-aadc-509e-0a342a5ba570@siemens.com> (raw)
In-Reply-To: <1571667598-657-1-git-send-email-Cedric_Hombourger@mentor.com>
On 21.10.19 16:19, Cedric Hombourger wrote:
> It appears that the last update of Isar we did was last year. I would like to propose that
> we re-align ourselves with upstream (this would fix some of the gitsm fetcher issues I have
> been facing). No changes to bitbake were required, they however changed their API and
> bitbake multiconfig:foo:bar no longer works (bitbake mc:foo:bar should be used instead).
> Documentation and code using the old syntax was changed. The RECIPE-API-CHANGELOG document
> was also changed. All changes were tested with our ci_build.sh script (no issues or failures
> were observed).
Just in case others run into this:
While the official syntax is now "mc:", bitbake still stupports
"multiconfig:" as compat solution. Well, except you actually provide
multiple configs: Only the first entry seems to be properly converted to
"mc:" internally, and all other targets will fail the build...
So, we need to switch completely in downstream multiconfig projects as
well (so far I only know of jailhouse-images). The required kas change
is submitted, will require a new release there, though.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2019-11-08 8:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 14:19 Cedric Hombourger
2019-10-21 14:19 ` [PATCH 1/1] bitbake: update " Cedric Hombourger
2019-10-22 7:36 ` Henning Schild
2019-10-22 7:41 ` Cedric Hombourger
2019-10-22 15:56 ` Baurzhan Ismagulov
2019-10-24 6:58 ` chombourger
2019-10-24 19:44 ` Baurzhan Ismagulov
2019-11-05 12:36 ` chombourger
2019-11-06 6:01 ` Baurzhan Ismagulov
2019-11-06 6:02 ` Cedric Hombourger
2019-11-08 8:05 ` Jan Kiszka [this message]
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=098e5cae-bd87-aadc-509e-0a342a5ba570@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Cedric_Hombourger@mentor.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