<br>Just did a "git pull" of kdevplatform and tried to build and it failed. Then I did a "make clean" then a make and still got the following error:<br><br>"/home/XMan/Documents/Projects/kdevelop4/src/kdevplatform/language/codegen/applychangeswidget.cpp: In member function ‘bool KDevelop::ApplyChangesWidget::applyAllChanges()’: <br>
/home/XMan/Documents/Projects/kdevelop4/src/kdevplatform/language/codegen/applychangeswidget.cpp:149:82: error: no matching function for call to ‘KDevelop::IDocumentController::documentForUrl()’<br>/home/XMan/Documents/Projects/kdevelop4/src/kdevplatform/interfaces/idocumentcontroller.h:77:47: note: candidate is: virtual KDevelop::IDocument* KDevelop::IDocumentController::documentForUrl(const KUrl&) const<br>
make[2]: *** [language/CMakeFiles/kdevplatformlanguage.dir/codegen/applychangeswidget.o] Error 1<br>make[1]: *** [language/CMakeFiles/kdevplatformlanguage.dir/all] Error 2"<br><br>I have been using gcc 4.5 in openSuSE 11.4 <br>
<br>Michael<br><br><div class="gmail_quote">On Thu, Aug 23, 2012 at 2:34 PM, Aleix Pol <span dir="ltr"><<a href="mailto:aleixpol@kde.org" target="_blank">aleixpol@kde.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">On Thu, Aug 23, 2012 at 8:28 PM, Andreas Pakulat <<a href="mailto:apaku@gmx.de">apaku@gmx.de</a>> wrote:<br>
> Hi,<br>
><br>
> On Thu, Aug 23, 2012 at 8:14 PM, Aleix Pol <<a href="mailto:aleixpol@kde.org">aleixpol@kde.org</a>> wrote:<br>
>> On Thu, Aug 23, 2012 at 8:05 PM, Andreas Pakulat <<a href="mailto:apaku@gmx.de">apaku@gmx.de</a>> wrote:<br>
>>> Hi,<br>
>>><br>
>>> On Thu, Aug 23, 2012 at 3:17 PM, Aleix Pol <<a href="mailto:aleixpol@kde.org">aleixpol@kde.org</a>> wrote:<br>
>>>> On Thu, Aug 23, 2012 at 2:03 PM, Andreas Pakulat <<a href="mailto:apaku@gmx.de">apaku@gmx.de</a>> wrote:<br>
>>>>> Hi,<br>
>>>>><br>
>>>>> I was just trying to create a new Qt/C++ CMake project but was kinda<br>
>>>>> confused by the categories presented to me. The left-most list was:<br>
>>>>><br>
>>>>> Python, Ruby, C++, KDE, Standard<br>
>>>>><br>
>>>>> Naturally I chose C++ but that only has KDE (i.e. real KDE stuff, like<br>
>>>>> plasma, KApplication etc.) and and qmake templates.<br>
>>>>><br>
>>>>> I then checked Standard and KDE since the other two categories are<br>
>>>>> clearly not what I want. Standard has only a C++/Terminal with CMake.<br>
>>>>> Interestingly the KDE entry does not have a single KDE-related<br>
>>>>> template, all of the three are CMake/C++ Qt templates - one for tests,<br>
>>>>> one for gui and one for non-gui apps.<br>
>>>>><br>
>>>>> Now before I whip up a bugreport:<br>
>>>>><br>
>>>>> Is this categorization intentional as outlined above?<br>
>>>>><br>
>>>>> Should the categories in KDevelop or kapptemplate be changed? (I'd<br>
>>>>> personally fix the kdevelop templates to use the language as first<br>
>>>>> option too)<br>
>>>>><br>
>>>> What KDE SDK version do you have? this changed some time ago...<br>
>>><br>
>>> Interesting, still 4.7.4, thought I updated to 4.8 on that machine already...<br>
>>><br>
>>>> The reasoning behind was that it's more clear to have what you're<br>
>>>> trying to achieve in the topmost level so that you can get all the<br>
>>>> options on how to do it in the end.<br>
>>><br>
>>> Ok, so intended is to have KDE and Standard as top-levels? If so, our<br>
>>> templates are incorrectly categorized still IMO. After all a<br>
>>> QtCore-CMake-C++ template has absolutely nothing to do with "KDE".<br>
>>> Those would better be in a Qt category I think.<br>
>><br>
>> Maybe so.<br>
>><br>
>> Qt wasn't split because when this change was done there was a lot of<br>
>> the frameworks decisions going on. I think that what we should end up<br>
>> having is only Qt for applications and KDE for backends stuff, like<br>
>> KIO. Or not.<br>
><br>
> I think I'm missing something here. Can you please look at<br>
> kdevelop/app_templates and tell me why those 3 rather simple<br>
> application templates are in a KDE category? I don't see how this has<br>
> anything to do with frameworks, even if we fast-forward a year when<br>
> frameworks are actually released those three templates are still plain<br>
> Qt templates that having nothing to do with KDE (or frameworks).<br>
> kapptemplate ships all the KDE-libraries using templates and I totally<br>
> agree that those should be in a KDE category.<br>
><br>
> Andreas<br>
><br>
> --<br>
> KDevelop-devel mailing list<br>
> <a href="mailto:KDevelop-devel@kdevelop.org">KDevelop-devel@kdevelop.org</a><br>
> <a href="https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel" target="_blank">https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel</a><br>
<br>
</div></div>Well... there's been a lot of discussions about what is a KDE<br>
application and what isn't. That's what I meant.<br>
<span class="HOEnZb"><font color="#888888"><br>
Aleix<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
--<br>
KDevelop-devel mailing list<br>
<a href="mailto:KDevelop-devel@kdevelop.org">KDevelop-devel@kdevelop.org</a><br>
<a href="https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel" target="_blank">https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel</a><br>
</div></div></blockquote></div><br>