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

23 lines
785 B
CMake
Raw Normal View History

Implementation of mousepad plugin CCMAIL: ahmedibrahimkhali@gmail.com
2014-06-27 14:41:47 +01:00
set(kdeconnect_mousepad_SRCS
mousepadplugin.cpp
)
find_package(XTest REQUIRED)
find_package(X11 REQUIRED)
Add FindLibFakeKey.cmake. The build system cannot guess that a new build dependency was added.
2014-08-27 14:35:21 +01:00
find_package(LibFakeKey REQUIRED)
[mousepad] Use QX11Info to get the Display Don't open a second Display, we can use the one used by Qt. Advantages are: we are on the correct Display, we don't open a Display connection on e.g. Wayland (it would succeed but not work as a connection to Xwayland would be opened) and we can drop the copy of fixx11h. It's also a prerequisite to properly split the implementation to support Wayland in a later change. REVIEW: 124230
2015-07-02 13:49:38 +01:00
find_package(Qt5X11Extras REQUIRED)
plugins/mousepad: At least KF5::Wayland 5.3.90 is required Fake input interface was added to KF5::Wayland only a couple of weeks ago, it has not been released yet with this feature. CCMAIL: mgraesslin@kde.org
2015-07-21 02:46:18 +01:00
find_package(KF5Wayland 5.3.90)
[mousepad] Integrate with KWayland for fake input support KWayland provides a FakeInput interface which KWin as a compositor supports. This can be used to fake input events on Wayland. As it's a KWin specific interface it won't work with other Wayland compositors. If the compositor does not support the required interface, the module just doesn't do anything. Support in the implementation is completely optional. Adding fake input events circumvents the Wayland security model. Because of that the interface is designed in a way that the security decision can be done by the compositor and can be delegated to the user. On first input event kdeconnect tries to "authenticate" with the compositor. This gives the compositor the possibility to e.g. ask the user whether it should be allowed. It's not done on startup or of load module as that would show such a message way to early and the user would not be able to connect it with his action on the smartphone. REVIEW: 124238
2015-07-03 08:25:34 +01:00
set(HAVE_WAYLAND ${KF5Wayland_FOUND})
configure_file(config-mousepad.h.cmake ${CMAKE_CURRENT_BINARY_DIR}/config-mousepad.h )
Implementation of mousepad plugin CCMAIL: ahmedibrahimkhali@gmail.com
2014-06-27 14:41:47 +01:00
Port away from KServiceTrader Uses KPluginLoader+KPluginMetadata instead. Describes plugins in json instead of desktop files. These desktop files are then embedded into the .so file. All the plugins will be in a kdeconnect/ directory, and those will be the ones to look for. Note it doesn't drop the KService dependency as KIOCore is a KDE Connect dependency as well. REVIEW: 123042
2015-03-19 15:36:53 +00:00
kdeconnect_add_plugin(kdeconnect_mousepad JSON kdeconnect_mousepad.json SOURCES ${kdeconnect_mousepad_SRCS})
Implementation of mousepad plugin CCMAIL: ahmedibrahimkhali@gmail.com
2014-06-27 14:41:47 +01:00
Add FindLibFakeKey.cmake. The build system cannot guess that a new build dependency was added.
2014-08-27 14:35:21 +01:00
include_directories(${XTEST_INCLUDE_DIRS} ${X11_INCLUDE_DIR} ${LibFakeKey_INCLUDE_DIRS})
Implementation of mousepad plugin CCMAIL: ahmedibrahimkhali@gmail.com
2014-06-27 14:41:47 +01:00
[mousepad] Integrate with KWayland for fake input support KWayland provides a FakeInput interface which KWin as a compositor supports. This can be used to fake input events on Wayland. As it's a KWin specific interface it won't work with other Wayland compositors. If the compositor does not support the required interface, the module just doesn't do anything. Support in the implementation is completely optional. Adding fake input events circumvents the Wayland security model. Because of that the interface is designed in a way that the security decision can be done by the compositor and can be delegated to the user. On first input event kdeconnect tries to "authenticate" with the compositor. This gives the compositor the possibility to e.g. ask the user whether it should be allowed. It's not done on startup or of load module as that would show such a message way to early and the user would not be able to connect it with his action on the smartphone. REVIEW: 124238
2015-07-03 08:25:34 +01:00
target_link_libraries(kdeconnect_mousepad kdeconnectcore Qt5::Gui Qt5::X11Extras ${X11_LIBRARIES} ${XTEST_LIBRARIES} ${LibFakeKey_LIBRARIES} KF5::I18n)
if(HAVE_WAYLAND)
target_link_libraries(kdeconnect_mousepad KF5::WaylandClient)
endif()
Reference in a new issue Copy permalink