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

List:       kde-panel-devel
Subject:    Re: [plasma-framework] /: Revert "Enabling C++11 flags for clang and gcc"
From:       Shaun Reich <sreich () kde ! org>
Date:       2013-06-28 11:33:43
Message-ID: CADVynFAbMybCej6vqff4aCUQ6UXdByHyGc=qhgZiuBxmF8-=qA () mail ! gmail ! com
[Download RAW message or body]

On Fri, Jun 28, 2013 at 7:08 AM, Kevin Ottens <ervin@kde.org> wrote:
> On Friday 28 June 2013 11:02:25 Ivan Čukić wrote:
>> On Friday 28 June 2013 08:13:32 Kevin Ottens wrote:
>> > Git commit 597397b41f5450f24ddc784e0faa13133fed6bd5 by Kevin Ottens.
>> > Committed on 28/06/2013 at 08:07.
>> > Pushed by ervin into branch 'master'.
>> >
>> > Revert "Enabling C++11 flags for clang and gcc"
>>
>> This request [1] got a green light by Aaron [2] and Martin [3].
>
> Just to clarify: It's not a "no-no" to using C++11, it's to make sure we're
> able to build without them.
>
>> We could set it only for the shell, and not for the whole repository.
>
> Is there a point of using libplasma2 out of the shell? Just wondering, could
> impact the decision.
>
> Assuming the answer to the question above is yes, then it could be a
> compromise indeed. *But* in that case the build of the shell would have to be
> automatically disabled when building without C++11 available.

What's the issue here? Isn't the point of a dependency (on C++11) to
make it required?

/me definitely thinks we should be moving forward on this front,
especially since the main compilers are feature complete now (clang
has excellent support for it).

--
Shaun Reich,
KDE Software Developer (kde.org)
_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

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