Le lundi 17 juin 2013 20:15:23 Albert Astals Cid a écrit : > Maybe we should just make sure the qdbus calls in startkde have the full > qualified path and that's it?
Ah! This is for the calls to qdbus from within startkde itself! Well spotted. You're thinking of using something like @QDBUS_EXECUTABLE@ in startkde.cmake and substituting that with the path to qdbus at install time? I guess that would work, if someone switches to another version of Qt in another prefix, he has to recompile everything anyway. But looking at startkde, the code in question runs after ksmserver exits, and waits for drkonqi instances to exit, using `qdbus` and `kreadconfig`. How about turning this shell code into C++ code, and making it part of ksmserver? After all we have C++/Qt/kdelibs APIs to write such stuff, without the need to write shell scripting with rudimentary tools :) There's also a check that the dbus session is available, but surely we'll error out soon enough if this isn't the case? -- David Faure, [email protected], http://www.davidfaure.fr Working on KDE, in particular KDE Frameworks 5
