From: "'Cedric Hombourger' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: Cedric Hombourger <cedric.hombourger@siemens.com>
Subject: [PATCH 0/2] use BPN instead of PN for PP
Date: Thu, 12 Sep 2024 10:27:39 +0200 [thread overview]
Message-ID: <20240912082741.354985-1-cedric.hombourger@siemens.com> (raw)
With 2ca3a7e5, sources are built only once and re-used when building
-native and -compat binary packages. The dpkg-raw class generates
a debian/rules file with ${PP}/image expanded: this causes build
of the -compat or -native variants to fail since /home/builder/${PN}
does not exist in the sbuild environment of -compat/-native.
Change the definition of PP to be /home/builder/${BPN} so that the
expanded value remains the same for all variants.
Having absolute paths in generated debian/rules files is obviously
questionable.
Cedric Hombourger (2):
refactor: remove duplicate definition of BPN
dpkg: use BPN instead of PN when defining PP
meta/classes/dpkg-base.bbclass | 2 +-
meta/classes/multiarch.bbclass | 2 --
meta/classes/sbuild.bbclass | 2 +-
meta/classes/sdk.bbclass | 1 -
meta/conf/bitbake.conf | 1 +
5 files changed, 3 insertions(+), 5 deletions(-)
--
2.39.2
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/20240912082741.354985-1-cedric.hombourger%40siemens.com.
next reply other threads:[~2024-09-12 8:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 8:27 'Cedric Hombourger' via isar-users [this message]
2024-09-12 8:27 ` [PATCH 1/2] refactor: remove duplicate definition of BPN 'Cedric Hombourger' via isar-users
2024-09-12 8:27 ` [PATCH 2/2] dpkg: use BPN instead of PN when defining PP 'Cedric Hombourger' via isar-users
2024-09-19 13:17 ` [PATCH 0/2] use BPN instead of PN for PP 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=20240912082741.354985-1-cedric.hombourger@siemens.com \
--to=isar-users@googlegroups.com \
--cc=cedric.hombourger@siemens.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