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 15:36:27 +0000 [thread overview]
Message-ID: <566AED7B.3060206@imgtec.com> (raw)
In-Reply-To: <20151211163013.1c10a143@free-electrons.com>
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.
Regards,
Vincent.
>
> Thomas
>
next prev parent reply other threads:[~2015-12-11 15:36 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 [this message]
2015-12-11 15:46 ` Jörg Krause
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=566AED7B.3060206@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