compile problem kdevelop-pg-qt

jay kdevelop at jxx.sk
Fri Jun 24 13:53:07 UTC 2011


this is the solution:


$ git diff
diff --git a/tests/CMakeLists.txt b/tests/CMakeLists.txt
index 4084076..686c1cf 100644
--- a/tests/CMakeLists.txt
+++ b/tests/CMakeLists.txt
@@ -8,6 +8,7 @@ set(testlocationtable_SRCS
 kde4_add_unit_test(testlocationtable ${testlocationtable_SRCS})
 target_link_libraries(testlocationtable
     ${QT_QTTEST_LIBRARY}
+    ${QT_QTCORE_LIBRARY}
 )
 
 set(testmemorypool_SRCS
@@ -16,13 +17,17 @@ set(testmemorypool_SRCS
 kde4_add_unit_test(testmemorypool ${testmemorypool_SRCS})
 target_link_libraries(testmemorypool
     ${QT_QTTEST_LIBRARY}
+    ${QT_QTCORE_LIBRARY}
 )
 
 set(benchmarks_SRCS
     benchmarks.cpp
 )
+
+
 kde4_add_unit_test(benchmarks ${benchmarks_SRCS})
 target_link_libraries(benchmarks
     ${QT_QTTEST_LIBRARY}
+    ${QT_QTCORE_LIBRARY}
 )




In my tests I missed the fact, that benchmarks compiled correctly and
the error was on next file.


fedora changes (since f14):

https://fedoraproject.org/wiki/UnderstandingDSOLinkChange




On 06/22/2011 05:18 PM, Milian Wolff wrote:
> On Wednesday 22 June 2011 16:47:51 jay wrote:
>> On 06/22/2011 04:37 PM, Milian Wolff wrote:
>>> On Wednesday 22 June 2011 16:11:35 jay wrote:
>>>> successfully compiled quanta, kphotoalbum, yakuake
>>>> or i don't really know what is a QT app :)
>>> ok then this works.
>>>
>>>> could be possibly a bug in kdev-pg-qt,
>>>> because some google results with this error result in upstream fixes.
>>> Do you use gold?
>> nope, or "no comprende" :)
>>
>>>  And try to add ${QT_QTCORE_LIBRARY} to the
>>>
>>> target_link_libraries in tests/CMakeLists.txt
>> I was trying that
>>
>> $ git diff
>> diff --git a/tests/CMakeLists.txt b/tests/CMakeLists.txt
>> index 4084076..f14330b 100644
>> --- a/tests/CMakeLists.txt
>> +++ b/tests/CMakeLists.txt
>> @@ -24,5 +24,6 @@ set(benchmarks_SRCS
>>  kde4_add_unit_test(benchmarks ${benchmarks_SRCS})
>>  target_link_libraries(benchmarks
>>      ${QT_QTTEST_LIBRARY}
>> +    ${QT_QTCORE_LIBRARY}
>>  )
> sorry then I have no clue what is going on - you'll need to hope for someone 
> else to shed some light on this issue.
>
> bye





More information about the KDevelop-devel mailing list