On Thu, 3 Sept 2026 at 11:45, Gustav Lindberg via
lists.openembedded.org <[email protected]>
wrote:
> --- a/meta/recipes-support/boost/boost.inc
> +++ b/meta/recipes-support/boost/boost.inc
> @@ -44,6 +44,7 @@ BOOST_LIBS = "\
> type_erasure \
> url \
> wave \
> + ${@bb.utils.contains('PACKAGECONFIG', 'asio', 'asio', '', d)} \
Adding asio to BOOST_LIBS enables asio as a header-only install? Then
it should not be subject to PACKAGECONFIG, it can simply be added
unconditionally like all other libraries.
> +PACKAGECONFIG[asio] = ",,"
Then this should be named 'asio-shared' as it is also used to build
and install a shared library.
> +do_compile:append() {
> + if ${@bb.utils.contains('PACKAGECONFIG', 'asio', '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
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. via PACKAGECONFIG_CONFARGS or BJAM_EXTRA).
You probably need to patch boost to do this, and send the needed patch
upstream.
> +do_install:append() {
> + if ${@bb.utils.contains('PACKAGECONFIG', 'asio', '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
> +}
Same here: no custom installation, boost itself should do it if it was enabled.
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#245022):
https://lists.openembedded.org/g/openembedded-core/message/245022
Mute This Topic: https://lists.openembedded.org/mt/121066420/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
