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 ]

On Fri, 4 Sept 2026 at 12:02, Gustav Lindberg via
lists.openembedded.org <[email protected]>
wrote:

> > 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.
>
> 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
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#245392): 
https://lists.openembedded.org/g/openembedded-core/message/245392
Mute This Topic: https://lists.openembedded.org/mt/121083580/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to