Boudewijn Rempt wrote: > Yes, exactly. I've tried to find some documenation about this change, but > apart from the rather unhelpful info in e.g. > http://www.cmake.org/cmake/help/v3.1/manual/cmake-generator-expressions.7.html > I couldn't find anything. I don't even understand why "cmake is moving > towards doing things at the target level".
You might also find http://www.cmake.org/cmake/help/v3.2/manual/cmake-buildsystem.7.html helpful to your understanding. > Hm, that doesn't sound too hopeful :-(. I haven't looked into what vc is yet. What is needed here is a SSCCE http://sscce.org/ which does something like cmake_minimum_required(VERSION 3.0) project(VcTest) set(CMAKE_AUTOMOC ON) set(CMAKE_INCLUDE_CURRENT_DIR ON) find_package(Qt5Core REQUIRED) find_package(Vc REQUIRED) add_executable(hello hello.cpp) target_link_libraries(hello Qt5Core) # Do whatever should be done with vc and demonstrate that that doesn't work. If a SSCCE exists, I'm more likely to be able to help you. From reading this thread, it appears that the needs of vc for the include directories are the same as a moc needs for the include directories. See how moc gets them using the JOIN generator expression in the QT5_CREATE_MOC_COMMAND macro here: http://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/Qt5CoreMacros.cmake#n97 So, the most efficient way to make progress on this issue is to create a SSCCE as I described above. That will make the problem be of a managable size. Thanks, Steve. _______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
