On Sunday 26 August 2012, David Faure wrote:
> kde-runtime has cmake/modules/MacroDBusAddActivationService.cmake
> which says
>
> macro(dbus_add_activation_service _sources)
> foreach (_i ${_sources})
> get_filename_component(_service_file ${_i} ABSOLUTE)
> string(REGEX REPLACE "\\.service.*$" ".service" _output_file ${_i})
> set(_target ${CMAKE_CURRENT_BINARY_DIR}/${_output_file})
> configure_file(${_service_file} ${_target})
> install(FILES ${_target} DESTINATION ${DBUS_SERVICES_INSTALL_DIR} )
> endforeach (_i ${ARGN})
> endmacro(dbus_add_activation_service _sources)
>
> Typical usage: see kde-runtime/kuiserver:
>
> dbus_add_activation_service(org.kde.kuiserver.service.in)
>
> where that file contains
> [D-BUS Service]
> Name=org.kde.kuiserver
> Exec=@CMAKE_INSTALL_PREFIX@/bin/kuiserver
>
> I would now need this in kdelibs (frameworks branch), in order to generate
> org.kde.kded5.service and install it, to allow launching kded5 via dbus
> auto- activation.
>
> Can this macro go into ECM? Or even cmake?
>
> It's basically useful for anyone making a dbus service with cmake -- not
> even necessarily using Qt.
So, should it be part of FindDBUS.cmake ?
This can then of course go into ECM.
If somebody (not me) volunteers to maintain it in cmake, it can also go into
cmake itself.
Alex
_______________________________________________
Kde-buildsystem mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kde-buildsystem
