public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: Jan Kiszka <jan.kiszka@web.de>, isar-users <isar-users@googlegroups.com>
Cc: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
Subject: Re: [PATCH v2] multiarch: Fix PN-to-BPN massaging
Date: Tue, 09 Apr 2024 08:25:29 +0300	[thread overview]
Message-ID: <ce4d07f2117af4ca19a638044ed64fc23a08435c.camel@ilbers.de> (raw)
In-Reply-To: <f67b7757-1984-4c0d-b2db-70b6a09e4260@web.de>

On Mon, 2024-04-01 at 15:17 +0200, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> SRC_URI and FILESPATH are differently built, thus can't be handled
> the
> same way when trying to translate PN to BPN. While entries in the
> former
> are space-separated, they are colon-separated in the latter.
> 
> Furthermore, the existing logic didn't properly split the entries,
> rather
> processed the complete string. That was surely not desired as well.
> 
> Account for all by handling the variables separately and by splitting
> them first. This fixes warnings like
> 
> WARNING: /build/../repo/meta-isar/recipes-core/images/isar-image-
> installer.bb: Unable to get checksum for isar-image-installer-native
> SRC_URI entry debian-configscript.sh: file could not be found
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> 
> Changes since v2:
>  - picked final patch from local queue, fixing SRC_URI regression
> 
>  meta/classes/multiarch.bbclass | 16 ++++++++++------
>  1 file changed, 10 insertions(+), 6 deletions(-)
> 
> diff --git a/meta/classes/multiarch.bbclass
> b/meta/classes/multiarch.bbclass
> index 5783b0bf..5c97453b 100644
> --- a/meta/classes/multiarch.bbclass
> +++ b/meta/classes/multiarch.bbclass
> @@ -46,12 +46,16 @@ python multiarch_virtclass_handler() {
>      # parse time, and parsing always happens for all build variants.
> So in those
>      # few variables, we automatically replace ${PN} with ${BPN}.
>      def fixup_pn_in_vars(d):
> -        vars = 'SRC_URI FILESPATH'.split()
> -        for var in vars:
> -            v = d.getVar(var, expand=False)
> -            if v is not None and '${PN}' in v:
> -                d.setVar(var + ':remove', v)
> -                d.appendVar(var, ' ' + v.replace('${PN}', '${BPN}'))
> +        v = d.getVar('SRC_URI', expand=False) or ''
> +        for uri in v.split():
> +            if '${PN}' in uri:
> +                d.setVar('SRC_URI' + ':remove', uri)
> +                d.appendVar('SRC_URI', ' ' + uri.replace('${PN}',
> '${BPN}'))
> +
> +        v = d.getVar('FILESPATH', expand=False) or ''
> +        for path in v.split(':'):
> +            if '${PN}' in path:
> +                d.appendVar('FILESPATH', ':' + path.replace('${PN}',
> '${BPN}'))
> 
>      # When building compat/native, the corresponding suffix needs to
> be
>      # propagated to all bitbake dependency definitions.
> --
> 2.35.3
> 

-- 
Applied to next, thanks.



      reply	other threads:[~2024-04-09  5:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01 13:17 Jan Kiszka
2024-04-09  5:25 ` Uladzimir Bely [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=ce4d07f2117af4ca19a638044ed64fc23a08435c.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=adriaan.schmidt@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@web.de \
    /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