Please review: cmake check for Cagibi

Friedrich W. H. Kossebau kossebau at
Wed Aug 25 23:46:28 CEST 2010

Hi Christophe,

Mardi, le 24 août 2010, à 21:45, Christophe Giboudeaux a écrit:
> Hi,
> Sorry but I still think it's a bad idea. macro_log_feature() should only
> report missing build dependencies or in the future we'll have all kind
> of not-so-useful messages about runtime deps in different modules.
> If Cagibi has no usefulness at build time, look for it at runtime only.
> a kFatal/kWarning was suggested last week.

Not sure you will want/see that kFatal/kWarning in a kded module :) (it's the 
kded module networkwatcher which tries to talk to cagibi)

> a README.packagers would be enough (that's what we have in eg. kdepim).

Added one on your proposal :)

From my experience as a developer it is very helpful to also have runtime 
dependencies in the configuration log (overview). I often checkout some other 
module to test it or try a fix. When the build configuration is run, I go and 
hunt down all missing packages. It would be very inconvenient if I would have 
to do so for the runtime dependencies in a different step/way. Also such code 
(from trunk/master) is often needing more current version of the dependencies, 
so it would be very helpful if the check for existance of proper versions is 
done automatically and in the same run.

Do you agree that for this usecase it would be nice to have it? E.g. using 
that solution offered by Maciej in this thread?

KDE Okteta - a simple hex editor -

More information about the Kde-buildsystem mailing list