Error with mocs in compiling kdevelop

[David Nolden]

Am Freitag, 11. August 2006 01:48 schrieb Eric Pignet:
> Hello,
>
> I have an error when compiling kdevelop svn. A kopete developer with whom I
> talked has exactly the same error.
> I use last cmake version, as given in
> http://developer.kde.org/build/trunk.html
> I compiled qt-copy and kdelibs successfully.
> But when trying to compile kdevelop, I get the following error:
>

I had the same! I solved it with the following patch!

-----------patch -------------------------------------------------
Index: kdevelop/lib/weaver/CMakeLists.txt
===================================================================
--- kdevelop/lib/weaver/CMakeLists.txt  (Revision 570911)
+++ kdevelop/lib/weaver/CMakeLists.txt  (Arbeitskopie)
@@ -23,6 +23,8 @@
     IncludeMocs.cpp
     JobCollection.cpp
     JobSequence.cpp
+#    Job.cpp
+#    Thread.cpp
     ${CMAKE_CURRENT_BINARY_DIR}/Job_moc.cpp
     ${CMAKE_CURRENT_BINARY_DIR}/Thread_moc.cpp
 )
@@ -34,11 +36,26 @@
 QT4_GET_MOC_INC_DIRS(_moc_INCS)

 add_custom_command(
+    OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/Job.moc
+    COMMAND ${QT_MOC_EXECUTABLE}
+    ARGS ${_moc_INCS} -f ${CMAKE_CURRENT_SOURCE_DIR}/Job.h -o 
${CMAKE_CURRENT_BINARY_DIR}/Job.moc
+    DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/Job.h
+)
+
+add_custom_command(
+    OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/Thread.moc
+    COMMAND ${QT_MOC_EXECUTABLE}
+    ARGS ${_moc_INCS} -f ${CMAKE_CURRENT_SOURCE_DIR}/Thread.h -o 
${CMAKE_CURRENT_BINARY_DIR}/Thread.moc
+    DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/Thread.h
+)
+
+add_custom_command(
     OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/Job_moc.cpp
     COMMAND ${QT_MOC_EXECUTABLE}
     ARGS ${_moc_INCS} -f ${CMAKE_CURRENT_SOURCE_DIR}/Job.cpp -o 
${CMAKE_CURRENT_BINARY_DIR}/Job_moc.cpp
     DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/Job.cpp
 )
+
 add_custom_command(
     OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/Thread_moc.cpp
     COMMAND ${QT_MOC_EXECUTABLE}


-----------patch end -------------------------------------------------

I just found it out by a lot of trying and don't know if it's correct so I 
only submitted it to my branch. :)

greetings, David