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 <[email protected]> > To: [email protected] > > 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 [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
