From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] package/boost: add library coroutine2
Date: Fri, 11 Dec 2015 16:18:43 +0000 [thread overview]
Message-ID: <566AF763.3030603@imgtec.com> (raw)
In-Reply-To: <1449849659.1950.13.camel@embedded.rocks>
Dear J?rg Krause,
On 11/12/15 16:00, J?rg Krause wrote:
> On Fr, 2015-12-11 at 16:46 +0100, J?rg Krause wrote:
>> Hi Vicente,
>> Hi Thomas,
>>
>> 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.
>
> Sorry, I got this wrong.
>
> What I really meant is that there would be no library name
> boost_coroutine2, but one named boost_coroutine, but only in case it is
> built. Since coroutine2 is just a bunch of header files as Thomas
> explained, no shared library named boost_coroutine is built at all.
>
> J?rg
>
understood, thanks for the clarification. Here you have my...
Reviewed-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
Tested-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
$ find output/staging/usr/include/boost/coroutine2/ -type f
output/staging/usr/include/boost/coroutine2/detail/pull_coroutine.ipp
output/staging/usr/include/boost/coroutine2/detail/pull_control_block.hpp
output/staging/usr/include/boost/coroutine2/detail/push_control_block.hpp
...
Regards,
Vincent.
next prev parent reply other threads:[~2015-12-11 16:18 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
2015-12-11 16:00 ` Jörg Krause
2015-12-11 16:18 ` Vicente Olivert Riera [this message]
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=566AF763.3030603@imgtec.com \
--to=vincent.riera@imgtec.com \
--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