This is not about resulting size of our lib. Moreover, we will not statically link it to Ignite because in this case users will have troubles when using both Boost and Ignite simultaneously. The problem is that if we use Boost, we will force users to have it on their machines during both build-time and runtime. And Boost is known to have dready dependencies between their modules. So if we use only concurrency module it might lead to transitive dependencies to lots other ones.
On Wed, May 20, 2015 at 9:46 AM, Pavel Tupitsyn <[email protected]> wrote: > Hi, > > I vote for Boost. From my understanding, it is the most comprehensive > extension library, and very widely adopted. > > What do you mean by "too heavy"? > > - Did you try to use it and compare dll sizes? How big is the > difference? > - Does dll size really matter for us that much? > > Thanks, > > On Wed, May 20, 2015 at 9:20 AM, Vladimir Ozerov <[email protected]> > wrote: > > > Igniters, > > > > In upcoming interop efforts we will need concurrent collections and > > primitives in C++ layer. Obvious candidate is Boost, but it appears to be > > too heavy. Another library I found is Intel's TBB ( > > https://www.threadingbuildingblocks.org/) - it is open-source and pretty > > light. > > > > Does anyone has other ideas on this? > > > > Vladimir. > > > > > > -- > -- > Pavel Tupitsyn > GridGain Systems, Inc. > www.gridgain.com >
