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
