Enabling C++11 for KDevelop 4.7

Milian Wolff mail at milianw.de
Tue Nov 5 00:04:03 UTC 2013

On Saturday 02 November 2013 21:15:43 Andreas Pakulat wrote:
> Hi,
> On Sat, Nov 2, 2013 at 2:42 PM, Milian Wolff <mail at milianw.de> wrote:
> > Me again ;-)
> > 
> > Another topic that was brought up before: I want to enable C++11 as a
> > _mandatory_ dependency for KDevelop 4.7 (i.e. current master) and upward.
> > The
> > just branched 4.6 is not affected by that.
> > 
> > I want to target the following compilers/features:
> > 
> > GCC 4.7: http://gcc.gnu.org/gcc-4.7/cxx0x_status.html
> > -> Even available in Debian Wheezy (stable)
> > 
> > Clang 3.1: http://clang.llvm.org/cxx_status.html
> > -> if I'm not mistaken has all the features of GCC 4.7
> Did you consider backporting the C++ 11 checks from Qt5? Ah, reading the
> rest you do. Wheezy is just a few months old, so might not be the best to
> base on. What about other Linux distro's like Fedora or OpenSuse? What does
> the current release contain and what does the last one have? Mac seems to
> have clang3.1 available in 10.8 and possibly even 10.7 with a recent-enough
> Xcode.

Since we are talking about KDevelop 4.7 here, it's perfectly fine if _current_ 
distros support it. We won't release until 2nd quarter of 2014 I bet. Thus I 
really don't care if an older Debian or $distro doesn't build it now.

FTR: Ubuntu raring and OpenSuse 12.3 have GCC 4.7, clang 3.2. Fedora 18 has 
clang 3.3 and GCC 4.7. All versions above those have either newer clang or 

> > This should cover all platforms where KDevelop is actually being used. In
> > my
> > opinion its more important to make our codebase attractive to new
> > developers
> > than trying to support the ugly software stepchild called Microsoft:
> > 
> > 
> > http://msdn.microsoft.com/en-us/library/vstudio/hh567368.aspx
> > -> Even 2013 is still missing as fundamental aspects as constexpr and
> > noexcept...
> > 
> > So the question is now whether we want to use the Qt macros like
> > and try to support MSVC 2013 or not... Personally I'd be OK with that if
> > people really think it's worth it. I simply don't think that we will get a
> > user base on Windows any time soon. This might change with KF5/Qt5 though,
> > at
> > which point I'm confident that Windows finally catched up with the other
> > compiler vendors. Note how rapid they are pumping out new releases which
> > actually add a lot of new features.
> My personal opinion for a KDE4 based KDevelop is: forget about Windows. Its
> simply too painful to setup a dev-env for a KDE4 app for anybody to be
> interested in that as a 'spare time project'. Its just not a supported
> platform for KDevelop at the moment.
> If KDevelop starts to use KF5 you could re-consider this decision if the
> frameworks KDevelop depends on dropped most/all of the huge dependency
> stack they currently have and setting up a suitable dev-env has become much
> easier (i.e. there are ready-made binaries that one can use to develop kde
> apps).
> Thats one of the major benefits that QtCreator has for me, its sooo much
> easier to build and patch it on that platform.

Jup, I see it the same way.

So, has anyone else any objections? Otherwise I'll enable C++11 in master on 

Milian Wolff
mail at milianw.de

More information about the KDevelop-devel mailing list