Bug 2516

Summary: boost: added missing libraries to BOOST_LIBS
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Johannes König <koenig>
Component: coreAssignee: Saul Wold <sgw>
Status: RESOLVED NOTABUG QA Contact:
Severity: normal    
Priority: Low CC: meta.mr.watcher, meta.watcher
Version: unspecified   
Target Milestone: 1.3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---
Attachments:
Description Flags
Patch none

Description Johannes König 2012-05-29 08:52:08 UTC
Created attachment 551 [details]
Patch

Some libraries included in Boost are not listed in the BOOST_LIBS variable (and therefor are not build). The attached patch adds these libraries to the recipe.

- chrono
- exception
- locale
- math
- random
- timer
Comment 1 Saul Wold 2012-06-05 07:01:59 UTC
Johannes,  We currently limit the libraries that are built for what is required by the other native tools that use boost so that we do not need have longer build time and larger binaries.

What's the reason for adding these additional libraries?  Are you working with a layer, can these be added to your layer via a .bbextend?

I am inclinded to close this
Comment 2 Johannes König 2012-06-05 11:42:46 UTC
Yes, I need it for my own recipes. You are right, it is better to extend boost only for my layer. You can close this ticket.

(Do you mean .bbappend with .bbextend?)

But I think in the future it would be better to split the monolithic boost recipe into multiple recipes. One recipe for each boost library which requires a build step and an additionally recipe for boost headers. This allows each recipe to define the dependencies with a finer granularity.
Comment 3 Saul Wold 2012-06-06 03:18:40 UTC
Yes, it was late when I wrote that, I meant the .bbappend file.  I would have to look at what it would take to split the boost package into seperate recipes, sounds like a worth goal, but maybe not for 1.3.

I will close this bug, if you want to open a new one for splitting the boost library that would be fine.