CMake and ksysguardd

John Tapsell johnflux at
Wed Sep 30 10:56:14 BST 2009

2009/9/30 Pau Garcia i Quiles <pgquiles at>:
> On Wed, Sep 30, 2009 at 10:38 AM, John Tapsell <johnflux at> wrote:
>> 2009/9/29 Pau Garcia i Quiles <pgquiles at>:
>> ..
>>>>  Could anyone that knows CMake help me with this :)
>>> It is not difficult to make it compile without KDE. The attached patch
>>> fixes and/or ignores the issues I pointed above.
>> It looks good.  How does this interact now with when people compile kdebase?
>> You still want "make install"  for example to install ksysguardd.
>> It's not important for "make install" to work if you run that just
>> inside the ksysguardd directory, if that helps.
>>> We could use an #ifdef or alike to be able to build ksysguardd with
>>> KDE (using config-workspace, etc) and without KDE (ignoring it). Would
>>> that be interesting for you ?
>  That patch was meant for you to take the ksysguardd directory and
> build it apart, not to apply it to the KDE svn repository.
> Would you be interested in being able to build ksysguardd
> independently from kdebase-workspace using the same CMakeLists.txt?

Exactly.  So that it builds as normal for most people, but distros can
easily package it as a seperate package that people can easily
recompile for their servers, embedded devices, etc.

> In that case, we'd need to to essentially what the patch does: copy the
> macros to a cmake directory (I don't know if this is acceptable by
> KDE's policy, CMake stuff is usually kept in a 'cmake' directory at
> the top level of the module, i. e. kdebase-workspace) and, instead of
> just commenting out the config-workspace.h uses, add an #ifdef.
>> I don't know - is it important to use config-workspace?
> I don't know, you tell me. The only time I looked at ksysguardd's
> code, I has horrified by the custom protocol it uses to communicate
> with the GUI :-)

Yes, it's pretty awful - but the protocol hasn't changed for many
years.  people have put ksysguardd on all sorts of devices to monitor

> (btw, why doesn't it use DBUS?)

ksysguardd just prints to stdout, meaning it can be piped across networks etc.

> --
> Pau Garcia i Quiles
> (Due to my workload, I may need 10 days to answer)

More information about the kde-core-devel mailing list