From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] package/boost: add library coroutine2
Date: Fri, 11 Dec 2015 16:46:44 +0100 [thread overview]
Message-ID: <1449848804.1950.7.camel@embedded.rocks> (raw)
In-Reply-To: <566AED7B.3060206@imgtec.com>
Hi Vicente,
Hi Thomas,
On Fr, 2015-12-11 at 15:36 +0000, Vicente Olivert Riera wrote:
> Hi Thomas,
>
> On 11/12/15 15:30, Thomas Petazzoni wrote:
> > Vicente,
> >
> > On Fri, 11 Dec 2015 15:08:26 +0000, Vicente Olivert Riera wrote:
> >
> > > I was trying to test your patch and I have noticed that despite
> > > of
> > > having coroutine2 selected...
> > >
> > > BR2_PACKAGE_BOOST_COROUTINE2=y
> > >
> > > ...there isn't any libboost_coroutine2.so file installed on
> > > target. Is
> > > that normal?
> >
> > The vast majority of Boost "libraries" are not libraries in the .so
> > sense, but purely header based libraries, i.e just a bunch of .h
> > with
> > very complicated C++ code.
>
> But there is a libboost_coroutine.so library, that's why I asked. Is
> it
> expected to have a lib for coroutine and not for coroutine2? That's
> my
> doubt.
The Jamfile for coroutine contains:
lib boost_coroutine
????: detail/coroutine_context.cpp
??????exceptions.cpp
??????stack_traits_sources
????: <link>shared:<library>../../context/build//boost_context
??????<link>shared:<library>../../system/build//boost_system
??????<link>shared:<library>../../thread/build//boost_thread
????;
While the Jamfile for coroutine2 contains:
lib boost_coroutine2
????:
????: <link>shared:<library>../../context/build//boost_context
????;
So, coroutine has some sources to link with, while coroutine2 does not.
Also, look at the config.hpp in coroutine2:
#if (defined(BOOST_ALL_DYN_LINK) ||
defined(BOOST_COROUTINES2_DYN_LINK) ) && !
defined(BOOST_COROUTINES2_STATIC_LINK)
# if defined(BOOST_COROUTINES2_SOURCE)
#??define BOOST_COROUTINES2_DECL BOOST_SYMBOL_EXPORT
#??define BOOST_COROUTINES2_BUILD_DLL
# else
#??define BOOST_COROUTINES2_DECL BOOST_SYMBOL_IMPORT
# endif
#endif
#if ! defined(BOOST_COROUTINES2_DECL)
# define BOOST_COROUTINES2_DECL
#endif
#if ! defined(BOOST_COROUTINES2_SOURCE) && !
defined(BOOST_ALL_NO_LIB) && ! defined(BOOST_COROUTINES2_NO_LIB)
# define BOOST_LIB_NAME boost_coroutine
# if defined(BOOST_ALL_DYN_LINK) ||
defined(BOOST_COROUTINES2_DYN_LINK)
#??define BOOST_DYN_LINK
# endif
# include <boost/config/auto_link.hpp>
#endif
For coroutine a library name is defined, for coroutine2 not.
J?rg
next prev parent reply other threads:[~2015-12-11 15:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 13:57 [Buildroot] [PATCH 1/3] package/boost: bump to version 1.59.0 Jörg Krause
2015-12-11 13:57 ` [Buildroot] [PATCH 2/3] package/boost: fix space tabs Jörg Krause
2015-12-11 14:48 ` Vicente Olivert Riera
2015-12-11 13:57 ` [Buildroot] [PATCH 3/3] package/boost: add library coroutine2 Jörg Krause
2015-12-11 15:08 ` Vicente Olivert Riera
2015-12-11 15:30 ` Thomas Petazzoni
2015-12-11 15:36 ` Vicente Olivert Riera
2015-12-11 15:46 ` Jörg Krause [this message]
2015-12-11 16:00 ` Jörg Krause
2015-12-11 16:18 ` Vicente Olivert Riera
2015-12-11 14:45 ` [Buildroot] [PATCH 1/3] package/boost: bump to version 1.59.0 Vicente Olivert Riera
2015-12-12 12:54 ` Thomas Petazzoni
2015-12-13 21:28 ` Thomas Petazzoni
2015-12-14 12:31 ` Jörg Krause
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1449848804.1950.7.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox