dependency on generated header (Fwd: [Kde-dashboard] Failed trunk/kdesupport r1027553)
Can someone remind me how to add a dependency on a generated header? tplugins.cpp (from taglib-extras) includes taglib_export.h (from toplevel/taglib) which includes the generated taglib_config.h (in toplevel/taglib too), a common problem for all buildsystems; afaik there is no way to detect that dependency automatically, it needs to be specified explicitely; but how? (I'm quite sure the problem is that the .h isn't generated yet; the include paths look correct, and this is also why it works for most people, without -j or with a smaller -j value) -- Forwarded Message -- Subject: [Kde-dashboard] Failed trunk/kdesupport r1027553 Date: Thursday 24 September 2009 From: Dirk Mueller muel...@kde.org To: kde-dashbo...@kde.org Running kdesupport build-test for revision 1027553 architecture head-i586 failed with: Scanning dependencies of target tag-extras [ 97%] Building CXX object taglib-extras/taglib-extras/CMakeFiles/tag- extras.dir/tplugins.cpp.o In file included from kdesupport-1027553/taglib/include/taglib_export.h:1, from kdesupport-1027553/taglib-extras/taglib-extras/tplugins.cpp:29: kdesupport-1027553/taglib/include/../taglib/taglib_export.h:39:27: error: taglib_config.h: No such file or directory make[2]: *** [taglib-extras/taglib-extras/CMakeFiles/tag-extras.dir/tplugins.cpp.o] Error 1 make[1]: *** [taglib-extras/taglib-extras/CMakeFiles/tag-extras.dir/all] Error 2 make: *** [all] Error 2 --- -- David Faure, fa...@kde.org, sponsored by Nokia to work on KDE, Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org). ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: dependency on generated header (Fwd: [Kde-dashboard] Failed trunk/kdesupport r1027553)
David Faure wrote: Can someone remind me how to add a dependency on a generated header? tplugins.cpp (from taglib-extras) includes taglib_export.h (from toplevel/taglib) which includes the generated taglib_config.h (in toplevel/taglib too), a common problem for all buildsystems; afaik there is no way to detect that dependency automatically, it needs to be specified explicitely; but how? If the header is supposed to be generated in another library or target than the one in which tplugins.cpp is built, just add a target-level dependency: # extras depends on the library api add_dependencies(tag-extras tag) If the header is generated in the same target, just list the header in the target's sources. -Brad -- Forwarded Message -- Subject: [Kde-dashboard] Failed trunk/kdesupport r1027553 Date: Thursday 24 September 2009 From: Dirk Mueller muel...@kde.org To: kde-dashbo...@kde.org Running kdesupport build-test for revision 1027553 architecture head-i586 failed with: Scanning dependencies of target tag-extras [ 97%] Building CXX object taglib-extras/taglib-extras/CMakeFiles/tag- extras.dir/tplugins.cpp.o In file included from kdesupport-1027553/taglib/include/taglib_export.h:1, from kdesupport-1027553/taglib-extras/taglib-extras/tplugins.cpp:29: kdesupport-1027553/taglib/include/../taglib/taglib_export.h:39:27: error: taglib_config.h: No such file or directory make[2]: *** [taglib-extras/taglib-extras/CMakeFiles/tag-extras.dir/tplugins.cpp.o] Error 1 make[1]: *** [taglib-extras/taglib-extras/CMakeFiles/tag-extras.dir/all] Error 2 make: *** [all] Error 2 --- ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: dependency on generated header (Fwd: [Kde-dashboard] Failed trunk/kdesupport r1027553)
On 24.09.09 13:07:17, David Faure wrote: Can someone remind me how to add a dependency on a generated header? tplugins.cpp (from taglib-extras) includes taglib_export.h (from toplevel/taglib) which includes the generated taglib_config.h (in toplevel/taglib too), a common problem for all buildsystems; afaik there is no way to detect that dependency automatically, it needs to be specified explicitely; but how? (I'm quite sure the problem is that the .h isn't generated yet; the include paths look correct, and this is also why it works for most people, without -j or with a smaller -j value) The config files are generated during cmake time. So a dependency is not needed. Are you sure that kdesupport-builddir/taglib/ is in the list of include's as I can't see that in the cmake files. So I guess taglib needs to be installed before building taglib-extras. Andreas -- You teach best what you most need to learn. ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: dependency on generated header (Fwd: [Kde-dashboard] Failed trunk/kdesupport r1027553)
On Thursday 24 September 2009, Andreas Pakulat wrote: The config files are generated during cmake time. So a dependency is not needed. Turns out you were correct. And the problem wasn't anything we could suspect from looking at the logs: the problem was a messed up checkout after a disk-full situation on the build server ;-) Thanks for the replies anyway. -- David Faure, fa...@kde.org, sponsored by Nokia to work on KDE, Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org). ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
