From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: alex.kiernan@gmail.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-Core] boost: Use PN/BPN for naming of packages
Date: Sun, 02 Mar 2025 12:34:44 +0000 [thread overview]
Message-ID: <169badfc1a6ee7e24975610a4166c58353a81667.camel@linuxfoundation.org> (raw)
In-Reply-To: <20250302074334.1775-1-alex.kiernan@gmail.com>
On Sun, 2025-03-02 at 07:43 +0000, Alex Kiernan via lists.openembedded.org wrote:
> boost-test and boost-serialization were hardcoded, switch to the ${PN} form.
> Also lookup ${BPN} when generating split package names. With these changes,
> generating an explicitly versioned boost package (e.g. "boost-1.82") alongside
> the main boost package ("boost") can be done by copying/renaming the older
> recipe. This is useful when upstream code hasn't yet been ported to newer
> boost and an older version is required.
>
> Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com>
> ---
> meta/recipes-support/boost/boost.inc | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/meta/recipes-support/boost/boost.inc b/meta/recipes-support/boost/boost.inc
> index 77105aa1fa13..458dfa9ac2fb 100644
> --- a/meta/recipes-support/boost/boost.inc
> +++ b/meta/recipes-support/boost/boost.inc
> @@ -69,7 +69,7 @@ python __anonymous () {
> mlprefix = d.getVar("MLPREFIX")
> for lib in d.getVar('BOOST_LIBS').split():
> extras.append("--with-%s" % lib)
> - pkg = "boost-%s" % (lib.replace("_", "-"))
> + pkg = "%s-%s" % (d.getVar("BPN"), lib.replace("_", "-"))
> if "-native" in pn:
> pkg = pkg + "-native"
> packages.append(mlprefix + pkg)
> @@ -86,9 +86,9 @@ python __anonymous () {
> FILES:${PN}-graph_parallel = "${libdir}/libboost_graph_parallel.so.*"
> FILES:${PN}-locale = "${libdir}/libboost_locale.so.*"
> FILES:${PN}-mpi = "${libdir}/mpi.so ${libdir}/libboost_mpi*.so.*"
> -FILES:boost-serialization = "${libdir}/libboost_serialization*.so.* \
> +FILES:${PN}-serialization = "${libdir}/libboost_serialization*.so.* \
> ${libdir}/libboost_wserialization*.so.*"
> -FILES:boost-test = "${libdir}/libboost_prg_exec_monitor*.so.* \
> +FILES:${PN}-test = "${libdir}/libboost_prg_exec_monitor*.so.* \
> ${libdir}/libboost_unit_test_framework*.so.*"
>
> # -dev last to pick up the remaining stuff
>
Sounds like a reasonable idea but:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/59/builds/1097
https://autobuilder.yoctoproject.org/valkyrie/#/builders/17/builds/1025
https://autobuilder.yoctoproject.org/valkyrie/#/builders/92/builds/1097
Cheers,
Richard
next prev parent reply other threads:[~2025-03-02 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 7:43 [OE-Core] boost: Use PN/BPN for naming of packages Alex Kiernan
2025-03-02 12:34 ` Richard Purdie [this message]
2025-03-02 13:12 ` Alex Kiernan
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=169badfc1a6ee7e24975610a4166c58353a81667.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kiernan@gmail.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox