tristan/kdeconnect-kde
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
kdeconnect-kde/plugins/telepathy/telepathy-cm/CMakeLists.txt

33 lines
857 B
CMake
Raw Normal View History

Merge telephonyplugin and telepathy plugin We now use the telepathy interface when it's available, and fall back to our custom dialog when it's not. This also makes the kdeconnect telepathy connection manager be completely decoupled from the kdeconnect code. CCMAIL: david@davidedmundson.co.uk
2016-06-22 10:40:31 +01:00
find_package(TelepathyQt5 0.9.5)
find_package(TelepathyQt5Service 0.9.7)
Telepathy integration This sends recieved text messages to any Telepathy client and allows the user to respond from there. This should work with both our clients and Empathy. An account on telepathy is created on activation. As Telepathy clients expect backends to be always running, this is started by the daemon to suppress client errors. The plugin system then talks to the same CM via use of a singleton accessor. Based on work by Alexandr Akulich then tidied up and rebased.
2014-11-30 01:52:43 +00:00
project(connectcm)
Move the Telepathy infrastructure at the plugin level At the moment, telepathy integration needs to be compiled within the daemon. This creates a rather aggressive dependency with Telepathy. This plugin proposes to move into a plugin, so that if the plugin isn't present, telepathy becomes out of the picture. REVIEW: 128149
2016-06-16 09:16:35 +01:00
add_executable(connectcm
main.cpp
Telepathy integration This sends recieved text messages to any Telepathy client and allows the user to respond from there. This should work with both our clients and Empathy. An account on telepathy is created on activation. As Telepathy clients expect backends to be always running, this is started by the daemon to suppress client errors. The plugin system then talks to the same CM via use of a singleton accessor. Based on work by Alexandr Akulich then tidied up and rebased.
2014-11-30 01:52:43 +00:00
connection.cpp
protocol.cpp
textchannel.cpp
kdeconnecttelepathyprotocolfactory.cpp
)
target_link_libraries(connectcm
Qt5::Core
${TELEPATHY_QT5_LIBRARIES}
${TELEPATHY_QT5_SERVICE_LIBRARIES}
)
Move the Telepathy infrastructure at the plugin level At the moment, telepathy integration needs to be compiled within the daemon. This creates a rather aggressive dependency with Telepathy. This plugin proposes to move into a plugin, so that if the plugin isn't present, telepathy becomes out of the picture. REVIEW: 128149
2016-06-16 09:16:35 +01:00
install (TARGETS connectcm DESTINATION ${CMAKE_INSTALL_LIBEXECDIR})
Telepathy integration This sends recieved text messages to any Telepathy client and allows the user to respond from there. This should work with both our clients and Empathy. An account on telepathy is created on activation. As Telepathy clients expect backends to be always running, this is started by the daemon to suppress client errors. The plugin system then talks to the same CM via use of a singleton accessor. Based on work by Alexandr Akulich then tidied up and rebased.
2014-11-30 01:52:43 +00:00
Fixed dbus-activation of telepathy connection manager service
2016-06-21 18:56:52 +01:00
file(WRITE ${CMAKE_BINARY_DIR}/org.freedesktop.Telepathy.ConnectionManager.kdeconnect.service "[D-BUS Service]
Name=org.freedesktop.Telepathy.ConnectionManager.kdeconnect
Exec=${KDE_INSTALL_FULL_LIBEXECDIR}/connectcm
")
Move the Telepathy infrastructure at the plugin level At the moment, telepathy integration needs to be compiled within the daemon. This creates a rather aggressive dependency with Telepathy. This plugin proposes to move into a plugin, so that if the plugin isn't present, telepathy becomes out of the picture. REVIEW: 128149
2016-06-16 09:16:35 +01:00
install(FILES ${CMAKE_BINARY_DIR}/org.freedesktop.Telepathy.ConnectionManager.kdeconnect.service DESTINATION share/dbus-1/services)
install(
FILES kdeconnect.manager
DESTINATION share/telepathy/managers
)
Reference in a new issue Copy permalink