boost: Add support for building boost-asio as a shared library
PATCH v8 1/1 boost: Add support for building boost-asio as a shared library
This is needed to build boost asio as a shared library rather than a header-only library, which is needed to save memory.
This can be enabled by adding PACKAGECONFIG:append = " asio-shared" to boost_%.bbappend.
--- meta/recipes-support/boost/boost.inc | 25 +++++++++++++++++++ .../boost/boost/boost_asio.cpp | 1 + 2 files changed, 26 insertions(+) create mode 100644 meta/recipes-support/boost/boost/boost_asio.cpp
meta/recipes-support/boost/boost.inc +25 -0
@@ -16,6 +16,7 @@ do_configure[cleandirs] = "${B}" BOOST_LIBS = "\ atomic \ + asio \ charconv \ chrono \ container \
@@ -51,11 +52,14 @@ BOOST_LIBS = "\ # optional libraries PACKAGECONFIG ??= "locale python" +PACKAGECONFIG[asio-shared] = ",," PACKAGECONFIG[locale] = ",,icu" PACKAGECONFIG[graph_parallel] = ",,,boost-mpi mpich" PACKAGECONFIG[mpi] = ",,mpich" PACKAGECONFIG[python] = ",,python3" +SRC_URI:append = " ${@bb.utils.contains('PACKAGECONFIG', 'asio-shared', 'file://boost_asio.cpp', '', d)}" + inherit python3-dir PYTHON_ROOT = "${STAGING_DIR_HOST}/${prefix}"
@@ -198,6 +202,20 @@ do_compile() { --debug-configuration } +do_compile:append() { + if ${@bb.utils.contains('PACKAGECONFIG', 'asio-shared', 'true', 'false', d)}; then + ${CXX} ${CPPFLAGS} ${CXXFLAGS} \ + -DBOOST_ASIO_DYN_LINK=1 \ + -I${S} \ + -fPIC \ + -shared \ + -Wl,-soname,libboost_asio.so.${PV} \ + ${UNPACKDIR}/boost_asio.cpp \ + ${LDFLAGS} \ + -o ${B}/libboost_asio.so.${PV} + fi +} + do_install() { cd ${S} b2 ${BJAM_OPTS} \
@@ -220,4 +238,11 @@ do_install() { } +do_install:append() { + if ${@bb.utils.contains('PACKAGECONFIG', 'asio-shared', 'true', 'false', d)}; then + install -Dm 0755 ${B}/libboost_asio.so.${PV} ${D}${libdir}/libboost_asio.so.${PV} + ln -sf libboost_asio.so.${PV} ${D}${libdir}/libboost_asio.so + fi +} + BBCLASSEXTEND = "native nativesdk"
meta/recipes-support/boost/boost/boost_asio.cpp new file +1 -0
@@ -0,0 +1 @@ +#include <boost/asio/impl/src.hpp>
Signature · 3 lines
2.43.0 Rename `asio` packageconfig flag to `asio-shared` and include asio in BOOST_LIBS unconditionally.
Quoted 5 lines
No custom compiler executions please. Building a shared library should be done by the boost build system itself, and enabled via a flag to it during
do_configure(e.g. viaPACKAGECONFIG_CONFARGSorBJAM_EXTRA). You probably need to patch boost to do this, and send the needed patch upstream.
I spent a day trying to get that to work, but it doesn't seem to be possible. Everything I tried either breaks the header-only version or doesn't build the shared library.
Quoted 8 lines · Gustav Lindberg via lists.openembedded.org
Quoted 5 lines
No custom compiler executions please. Building a shared library should be done by the boost build system itself, and enabled via a flag to it during
do_configure(e.g. viaPACKAGECONFIG_CONFARGSorBJAM_EXTRA). You probably need to patch boost to do this, and send the needed patch upstream.I spent a day trying to get that to work, but it doesn't seem to be possible. Everything I tried either breaks the header-only version or doesn't build the shared library.
The next step is to ask boost upstream to help, maybe by filing a ticket, and/or continue maintaining a .bbappend with these changes.
I know boost is horrible, and has a convoluted non-standard boost-specific build system, but we should not be bypassing that entirely, especially when no one else is asking for asio-shared for now.
Adding asio to BOOST_LIBS is fine, and can go in as a separate patch. Can you send that please?
Alex
Hi,
I discussed this with my team and we don't think it's worth spending any more time on trying to patch boost. So we will create a recipe in our own code for building the shared library instead of publishing it here.
Best regards,
Gustav Lindberg
________________________________
Från: Alexander Kanavin <[email protected]>
Skickat: den 4 september 2026 14:53
Till: Gustav Lindberg <[email protected]>
Kopia: [email protected] <[email protected]> Ämne: Re: [OE-core] [PATCHv8] boost: Add support for building boost-asio as a shared library
[You don't often get email from [email protected]. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
Quoted 8 lines · Gustav Lindberg via lists.openembedded.org
Quoted 5 lines
No custom compiler executions please. Building a shared library should be done by the boost build system itself, and enabled via a flag to it during
do_configure(e.g. viaPACKAGECONFIG_CONFARGSorBJAM_EXTRA). You probably need to patch boost to do this, and send the needed patch upstream.I spent a day trying to get that to work, but it doesn't seem to be possible. Everything I tried either breaks the header-only version or doesn't build the shared library.
The next step is to ask boost upstream to help, maybe by filing a ticket, and/or continue maintaining a .bbappend with these changes.
I know boost is horrible, and has a convoluted non-standard boost-specific build system, but we should not be bypassing that entirely, especially when no one else is asking for asio-shared for now.
Adding asio to BOOST_LIBS is fine, and can go in as a separate patch. Can you send that please?
Alex
Quoted 8 lines · Gustav Lindberg via lists.openembedded.org
This is needed to build boost asio as a shared library rather than a header-only library, which is needed to save memory.
This can be enabled by adding
PACKAGECONFIG:append = " asio-shared"toboost_%.bbappend.Signed-off-by Gustav Lindberg <[email protected]>---
Hi Gustav,
It looks like this is not working as expected:
ERROR: boost-1.92.0-r0 do_compile: Execution of '/srv/pokybuild/yocto-worker/genericx86-64/build/build/tmp/work/core2-64-poky-linux/boost/1.92.0/temp/run.do_compile.1669567' failed with exit code 1
...
| notice: Searching '.' for project-config configuration file 'project-config.jam'. | notice: Loading project-config configuration file 'project-config.jam' from '.'. | error: wrong library name 'asio' in the --with-<library> option. | WARNING: exit code 1 from a shell command.
https://autobuilder.yoctoproject.org/valkyrie/#/builders/4/builds/4599
Can you have a look at the issue?
Thanks,
Mathieu
Signature · 3 lines
Mathieu Dubois-Briand, Bootlin Embedded Linux and Kernel engineering https://bootlin.com