Review Request: Add new variable in KDELibsDependencies.cmake to remove libutempter build-dependency from kwrited

George Kiagiadakis at
Thu Dec 31 12:10:32 GMT 2009

This is an automatically generated e-mail. To reply, visit:

Review request for kdelibs and Alexander Neundorf.


When building kwrited, it is required to know whether kpty has been built with utempter support or not.  This is because if it has, kwrited can be built as a kded module, otherwise it needs to be run with setuid root and thus it needs to be a separate process (built as a separate executable). Currently there is a check in kwrited that checks whether utempter is installed on the system, which is wrong, because that doesn't tell us if kpty has been built with it and adds an extra build-dependency on workspace for people that want to build kwrited as a kded module. This patch adds a variable in the KDELibsDependencies.cmake file which indicates whether kpty has been built with utempter or not.

I'm asking for review because I'm not sure whether adding such a variable in KDELibsDependencies.cmake is ok or I should find another way to do it.


  trunk/KDE/kdebase/workspace/kwrited/CMakeLists.txt 1065863 
  trunk/KDE/kdelibs/CreateKDELibsDependenciesFile.cmake 1065822 



I have built kdelibs and kdebase/workspace with and without utempter and kwrited builds either as a kded module or as an executable as expected.



More information about the kde-core-devel mailing list