[prev in list] [next in list] [prev in thread] [next in thread] 

List:       taglib-devel
Subject:    Re: Can TagLib2.0 require C++11 or Boost?
From:       Kyle <gonemad () gmail ! com>
Date:       2013-11-17 23:32:21
Message-ID: CADALLbCQ5TuGHhGbne1m0u1_iraOVYWgOW_ZLRQ9jWxfHs+ayQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


While i havent tried it,  it also might be a pain in the ass to get boost
to build with the android ndk
On Nov 17, 2013 6:28 PM, "Kyle" <gonemad@gmail.com> wrote:

> Please do not require boost.  Im fine with c++11 but boost would most
> likely increase the binary size by a lot which is something that mobile
> devs like myself cannot afford
> On Nov 17, 2013 6:20 PM, "Tsuda Kageyu" <tsuda.kageyu@gmail.com> wrote:
>
>>
>> Hi guys.
>>
>> I'm thinking about making changes that requires at least one of C++11 or
>> Boost Smart Pointers to TagLib 2.0.
>>
>> Currently, TagLib2 has self-implemented smart pointers when neither
>> std::shared_ptr nor boost::shared_ptr is available. I will remove it to
>> make TagLib more robust (and hopefully more efficient) by leaving all
>> the atomic operations for reference counting to the standard library or
>> Boost, but it also means to abandon some old compilers that Boost
>> doesn't support.
>>
>> So I'd like to ask you what kind of compilers are you using to build
>> TagLib. Is somebody using the compilers which are not supported by
>> Boost?
>>
>> This change only affects the users who builds TagLib themselves. It
>> doesn't affect the people who uses TagLib as a package.
>>
>> Kageyu.
>> _______________________________________________
>> taglib-devel mailing list
>> taglib-devel@kde.org
>> https://mail.kde.org/mailman/listinfo/taglib-devel
>>
>

[Attachment #5 (text/html)]

<p dir="ltr">While i havent tried it,  it also might be a pain in the ass to get \
boost to build with the android ndk</p> <div class="gmail_quote">On Nov 17, 2013 6:28 \
PM, &quot;Kyle&quot; &lt;<a href="mailto:gonemad@gmail.com">gonemad@gmail.com</a>&gt; \
wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> <p dir="ltr">Please do not require \
boost.  Im fine with c++11 but boost would most likely increase the binary size by a \
lot which is something that mobile devs like myself cannot afford</p> <div \
class="gmail_quote">On Nov 17, 2013 6:20 PM, &quot;Tsuda Kageyu&quot; &lt;<a \
href="mailto:tsuda.kageyu@gmail.com" target="_blank">tsuda.kageyu@gmail.com</a>&gt; \
wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">

<br>
Hi guys.<br>
<br>
I&#39;m thinking about making changes that requires at least one of C++11 or<br>
Boost Smart Pointers to TagLib 2.0.<br>
<br>
Currently, TagLib2 has self-implemented smart pointers when neither<br>
std::shared_ptr nor boost::shared_ptr is available. I will remove it to<br>
make TagLib more robust (and hopefully more efficient) by leaving all<br>
the atomic operations for reference counting to the standard library or<br>
Boost, but it also means to abandon some old compilers that Boost<br>
doesn&#39;t support.<br>
<br>
So I&#39;d like to ask you what kind of compilers are you using to build<br>
TagLib. Is somebody using the compilers which are not supported by<br>
Boost?<br>
<br>
This change only affects the users who builds TagLib themselves. It<br>
doesn&#39;t affect the people who uses TagLib as a package.<br>
<br>
Kageyu.<br>
_______________________________________________<br>
taglib-devel mailing list<br>
<a href="mailto:taglib-devel@kde.org" target="_blank">taglib-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/taglib-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/taglib-devel</a><br> \
</blockquote></div> </blockquote></div>



_______________________________________________
taglib-devel mailing list
taglib-devel@kde.org
https://mail.kde.org/mailman/listinfo/taglib-devel


[prev in list] [next in list] [prev in thread] [next in thread]