dependency on generated header (Fwd: [Kde-dashboard] Failed trunk/kdesupport r1027553)
Andreas Pakulat
apaku at gmx.de
Thu Sep 24 13:28:52 CEST 2009
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.
More information about the Kde-buildsystem
mailing list