Skip to contentSkip to conversation

boost: Use PN/BPN for naming of packages

OE-Core Alex Kiernan 2 participants 3 messages Mar 2, 2025

lore
Share & tools
lore
#0 lore raw

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.

---
 meta/recipes-support/boost/boost.inc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
meta/recipes-support/boost/boost.inc +3 -3
index 77105aa1fa13..458dfa9ac2fb 100644
@@ -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
#1 lore raw
Quoted 34 lines · Alex Kiernan via lists.openembedded.org

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.

---
 meta/recipes-support/boost/boost.inc | 6 +++---

 1 file changed, 3 insertions(+), 3 deletions(-)
meta/recipes-support/boost/boost.inc +0 -0
index 77105aa1fa13..458dfa9ac2fb 100644
@@ -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)

meta/recipes-support/boost/boost.inc +0 -0
@@ -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.*"

meta/recipes-support/boost/boost.inc +1 -1
-FILES:boost-serialization = "${libdir}/libboost_serialization*.so.* \
+FILES:${PN}-serialization = "${libdir}/libboost_serialization*.so.* \

  ${libdir}/libboost_wserialization*.so.*"

meta/recipes-support/boost/boost.inc +1 -1
-FILES:boost-test = "${libdir}/libboost_prg_exec_monitor*.so.* \
+FILES:${PN}-test = "${libdir}/libboost_prg_exec_monitor*.so.* \
Quoted 4 lines

  ${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

#2 lore raw
Quoted 38 lines · Richard Purdie
Quoted 36 lines · Alex Kiernan via lists.openembedded.org

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.

---
 meta/recipes-support/boost/boost.inc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
meta/recipes-support/boost/boost.inc +3 -3
index 77105aa1fa13..458dfa9ac2fb 100644
@@ -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.*"
 
Quoted 9 lines

meta/recipes-support/boost/boost.inc python __anonymous () { · line 94

Quoted 2 lines
meta/recipes-support/boost/boost.inc +0 -0
 # -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

Looks like multilib, which I'm not building locally :| Will have a look.

Signature · 1 line
Alex Kiernan