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
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
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
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
