Kdev-clang master not building
Lucas Tanure
tanure at linux.com
Sun May 10 00:02:31 UTC 2015
My source :
tanure at archDesk *kdevplatform* $ git show HEAD
commit *91001b610c4a6f095aee18d9cb0318e9ed5f0c2d*
Author: Aleix Pol <aleixpol at kde.org>
Date: Thu May 7 15:45:30 2015 +0200
Sort the run configurations within the submenus as well
tanure at archDesk *kdevelop* $ git show HEAD
commit *5feb236c049680809075bc9af616d40b9fbbd935*
Merge: d9a8814 ec1b9e7
Author: Milian Wolff <mail at milianw.de>
Date: Wed May 6 23:50:57 2015 +0200
Merge remote-tracking branch 'origin/4.7'
tanure at archDesk *kdev*-*clang* $ git show HEAD
commit *433f7cba94f1edb17db6e68256c7d722e3c3e8c9*
Author: Sergey Kalinichev <kalinichev.so.0 at gmail.com>
Date: Tue May 5 20:08:03 2015 +0400
Change kind for type aliases to Declaration::Type.
This enables highlighting of typedef's.
REVIEW: 123644
--
Lucas Tanure
+55 (19) 988176559
On Sat, May 9, 2015 at 8:57 PM, Lucas Tanure <tanure at linux.com> wrote:
> Hi,
>
> I tried to compile today but I got and Error. The error is the same.
> I tried to clean everything, but didn't solved.
>
> [ 81%] Building CXX object
> tests/CMakeFiles/test_codecompletion.dir/test_codecompletion.cpp.o
> In file included from /usr/include/qt/QtCore/qnamespace.h:37:0,
> from /usr/include/qt/QtCore/qobjectdefs.h:41,
> from /usr/include/qt/QtCore/qobject.h:40,
> from /usr/include/qt/QtCore/QObject:1,
> from
> /home/tanure/workspace/src/kdev-clang/tests/test_codecompletion.h:25,
> from
> /home/tanure/workspace/src/kdev-clang/tests/test_codecompletion.cpp:23:
> /usr/include/qt/QtCore/qmetatype.h: In instantiation of ‘constexpr int
> qMetaTypeId() [with T = KTextEditor::Cursor]’:
> /home/tanure/workspace/src/kdev-clang/tests/test_codecompletion.cpp:441:5:
> required from here
> /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
> Q_STATIC_ASSERT_X(QMetaTypeId2<T>::Defined, "Type is not registered,
> please use the Q_DECLARE_METATYPE macro to make it known to Qt's
> meta-object system");
> ^
> In file included from /usr/include/qt/QtCore/qobject.h:48:0,
> from /usr/include/qt/QtCore/QObject:1,
> from
> /home/tanure/workspace/src/kdev-clang/tests/test_codecompletion.h:25,
> from
> /home/tanure/workspace/src/kdev-clang/tests/test_codecompletion.cpp:23:
> /usr/include/qt/QtCore/qmetatype.h: In instantiation of ‘static constexpr
> int QMetaTypeId2<T>::qt_metatype_id() [with T = KTextEditor::Cursor]’:
> /usr/include/qt/QtCore/qmetatype.h:1649:44: required from ‘constexpr int
> qMetaTypeId() [with T = KTextEditor::Cursor]’
> /home/tanure/workspace/src/kdev-clang/tests/test_codecompletion.cpp:441:5:
> required from here
> /usr/include/qt/QtCore/qmetatype.h:1509:97: error: ‘qt_metatype_id’ is not
> a member of ‘QMetaTypeId<KTextEditor::Cursor>’
> static inline Q_DECL_CONSTEXPR int qt_metatype_id() { return
> QMetaTypeId<T>::qt_metatype_id(); }
>
> ^
> /usr/include/qt/QtCore/qmetatype.h:1509:100: error: body of constexpr
> function ‘static constexpr int QMetaTypeId2<T>::qt_metatype_id() [with T =
> KTextEditor::Cursor]’ not a return-statement
> static inline Q_DECL_CONSTEXPR int qt_metatype_id() { return
> QMetaTypeId<T>::qt_metatype_id(); }
>
> ^
> tests/CMakeFiles/test_codecompletion.dir/build.make:54: recipe for target
> 'tests/CMakeFiles/test_codecompletion.dir/test_codecompletion.cpp.o' failed
> make[2]: ***
> [tests/CMakeFiles/test_codecompletion.dir/test_codecompletion.cpp.o] Error 1
> CMakeFiles/Makefile2:833: recipe for target
> 'tests/CMakeFiles/test_codecompletion.dir/all' failed
> make[1]: *** [tests/CMakeFiles/test_codecompletion.dir/all] Error 2
> Makefile:126: recipe for target 'all' failed
> make: *** [all] Error 2
>
>
> Thanks
>
> --
> Lucas Tanure
> +55 (19) 988176559
>
> On Sun, May 3, 2015 at 5:14 AM, Kevin Funk <kfunk at kde.org> wrote:
>
>> On Monday, April 27, 2015 14:54:38 Milian Wolff wrote:
>> > On Monday 27 April 2015 10:37:04 Milian Wolff wrote:
>> > > On Monday 27 April 2015 10:05:28 Kevin Funk wrote:
>> > > > On Sunday, April 26, 2015 23:46:32 Aleix Pol wrote:
>> > > > > 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).
>> > > >
>> > > > That doesn't match my impression of Kubuntu. And which I just got
>> > > > confirmed
>> > > > by Riddell & Harald on IRC:
>> > > >
>> > > > - Kubuntu 15.04 is shipping KF5.9
>> > > > - It will very likely stay at that version (i.e. no updates),
>> > > >
>> > > > b/c of the manpower/"paperwork" it takes to update frameworks
>> > > >
>> > > > - SICs or other compatibility breaks in KF5 doesn't make it easier
>> for
>> > > > them
>> > > > to transition to newer KF5 releases, obviously
>> > > >
>> > > > Honestly, I don't see the reason why we should break compatibility
>> with
>> > > > KF5.9, which appears to be an attractive target given that Ubuntu is
>> > > > shipping it.
>> > > >
>> > > > And this is for one simple reason: If people need to compile/install
>> > > > dependencies to work on KDevelop5, it's always a hassle for them
>> (cf.
>> > > > this
>> > > > thread). Let's just make it easier for them.
>> > > >
>> > > > I'll add the compatibility code to kdev-clang if no-one else steps
>> up to
>> > > > do
>> > > > it (it's really not a big deal).
>> > >
>> > > I agree. Sorry for the hassle I introduced here, I assumed people will
>> > > build KF5 if they want to try out KDev and thus we are free to depend
>> on
>> > > the latest and greatest. Having a popular distro out in the open that
>> > > won't update for some time it's OK to uglify our code for half a year
>> > > with the macro guards.
>> > >
>> > > Kevin, I'll do this if you don't beat me to it later today or so.
>> > > KDevplatform also needs it afaik.
>> >
>> > Fixed now, please test.
>> >
>> > Bye
>>
>> Thanks for fixing, by the way.
>>
>> Cheers
>>
>> --
>> Kevin Funk | kfunk at kde.org | http://kfunk.org
>>
>> _______________________________________________
>> KDevelop-devel mailing list
>> KDevelop-devel at kde.org
>> https://mail.kde.org/mailman/listinfo/kdevelop-devel
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20150509/86226b8a/attachment.html>
More information about the KDevelop-devel
mailing list