Skip to contentSkip to conversation

boost: add lzma and zstd PACKAGECONFIG options

PATCH In review Divyanshu Rathore 2 participants 2 messages Oct 19 – Oct 22

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 boost: add lzma and zstd PACKAGECONFIG options

Add optional LZMA and Zstandard support to Boost.Iostreams for applications to read and write .xz and .zst compressed data.
Keeping them optional lets distributions enable interoperability with those widely used compression formats without adding the dependencies to all Boost builds.

Add optional PACKAGECONFIG entries for xz and zstd so Boost.Iostreams can be built with support for LZMA and Zstandard compressed streams.

---
 meta/recipes-support/boost/boost.inc | 2 ++
 1 file changed, 2 insertions(+)
meta/recipes-support/boost/boost.inc +2 -0
index c34b9c3e3e..ddb4b287ee 100644
@@ -56,6 +56,8 @@ PACKAGECONFIG[graph_parallel] = ",,,boost-mpi mpich"
 PACKAGECONFIG[mpi] = ",,mpich"
 PACKAGECONFIG[numpy] = ",,python3-numpy"
 PACKAGECONFIG[python] = ",,python3"
+PACKAGECONFIG[lzma] = ",,xz"
+PACKAGECONFIG[zstd] = ",,zstd"
 
 inherit python3-dir
 PYTHON_ROOT = "${STAGING_DIR_HOST}/${prefix}"
Signature · 1 line
2.43.0
#1 lore raw

meta/recipes-support/boost/boost.inc PACKAGECONFIG[graph_parallel] = ",,,boost-mpi mpich" · line 61

Quoted 9 lines · Divyanshu Rathore via lists.openembedded.org
meta/recipes-support/boost/boost.inc +2 -0
@@ -56,6 +56,8 @@ PACKAGECONFIG[graph_parallel] = ",,,boost-mpi mpich"
 PACKAGECONFIG[mpi] = ",,mpich"
 PACKAGECONFIG[numpy] = ",,python3-numpy"
 PACKAGECONFIG[python] = ",,python3"
+PACKAGECONFIG[lzma] = ",,xz"
+PACKAGECONFIG[zstd] = ",,zstd"
 

How do these new options work though? Other PACKAGECONFIG options are handled elsewhere in the boost recipe with custom code.

Are the newly ones relying on boost quietly detecting the compressors in sysroot and then enabling them in its own build? This is unreliable: these components can be placed in sysroot by transitive dependencies, and then they will be enabled by boost even when they're not enabled in the build configuration. You need to make it deterministic by figuring out what upstream does, and enforcing both enable and disable from the recipe, e.g. via build options or writing out a build config file.

Alex