Kdev-clang master not building

Aleix Pol aleixpol at kde.org
Sun Apr 26 21:46:32 UTC 2015

On Sun, Apr 26, 2015 at 4:51 PM, Andreas Pakulat <apaku at gmx.de> wrote:
> Hi Milian,
> On Sun, Apr 26, 2015 at 3:08 PM, Milian Wolff <mail at milianw.de> wrote:
>> On Saturday 25 April 2015 09:46:39 Lucas Tanure wrote:
>> > /usr/include/qt/QtCore/qmetatype.h:1648:5: error: static assertion
>> > failed: Type is not registered, please use the Q_DECLARE_METATYPE
>> > macro to make it known to Qt's meta-object system
>> Are you building KF5 yourself or are you using a distro package? I cleaned
>> up
>> the KTextEditor framework to offer this in range.h/cursor.h there. So, if
>> possible, update your KTextEditor framework. Otherwise, I'll add the
>> metatype
>> declaration again in macro guards.
> Is there a general consensus on wether kdevelop/kdevplatform is allowed to
> depend on frameworks master branches? That is, are you expecting all
> contributors to build kf5 from git until the first release?
> Andreas
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kdevelop-devel

It hasn't been discussed yet.

Maybe we could require the last KF5 released version.
In Plasma master, KF5 master is required and for frameworks the last
released version at the .0 release date.

The plan is to have distributions packaging newer KF5 versions as they
are released. (and it's already happening for Kubuntu and ArchLinux,
at least).

If we consider it's stopping people from developing kdevelop5, we can
always decide to require the last released KF5 version.


More information about the KDevelop-devel mailing list