vitalif
/
kwin
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
kwin/config-kwin.h.cmake

31 lines
1005 B
CMake
Raw Normal View History

Do not try to load plugin when building without decos
2011-04-29 14:34:22 +04:00
#cmakedefine KWIN_BUILD_DECORATIONS 1
Provide build option for TabBox functionality Since the TabBox functionality is not feasible for any platform KWin is used on (e.g. tablet PCs), a build option is added to decide, if the TabBox functionality should be build or not. REVIEW: 101511 @Sebastian: Martin wanted me to let you know that it is now possible to disable building Tabbox CCMAIL: sebas@kde.org
2011-06-30 15:02:30 +04:00
#cmakedefine KWIN_BUILD_TABBOX 1
Introducing a build option for KActivities support REVIEW: 104100
2012-02-26 14:38:16 +04:00
#cmakedefine KWIN_BUILD_ACTIVITIES 1
Add CMake variable to rename kwin binaries A CMake variable is used to specify the name of the binary. By default this is "kwin" but building for PA changes the name to "kwinactive". The variable adjusts all names, e.g. kwinnvidiahack becomes kwinactivenvidiahack. The remaining usage of kwinrc in core and libs is replaced by a cmakedefine for the configuration name and all data installations are moved to the defined name. Dynamic loading for scripts & co is adjusted for loading based on defined name. This change allows the side-by-side installation of both kwin for desktop and kwin for Plasma Desktop without the known issues like conflicts in config files or missing build options if kwin desktop is used for Plasma Active. Likewise the KCMs are not adjusted as they are not intended to be used for kwinactive. REVIEW: 104299 BUG: 296084 FIXED-IN: 4.9.0 CCMAIL: active@kde.org
2012-03-16 11:37:09 +04:00
#define KWIN_NAME "${KWIN_NAME}"
Rename KWin binary to kwin_x11 This servers two purposes. 1. it makes KWin/5 co-installable with KWin/4 as now binary and all libraries etc. are renamed or installed to a different location. 2. In future we need a dedicated X11 and Wayland main function anyway. Thus it makes most sense to rename to kwin_x11 directly instead of first renaming to kwin5. The reason why we need to have dedicated main functions is that kwin needs to check early whether X11 is working or Wayland is working. Right now the first thing kwin does is trying to connect to the XServer. This happens before the QApplication is constructed and before command line args are processed. On Wayland we won't want to test whether we can connect to the XServer. As it's too early to check whether we are starting kwin for X11 or Wayland the most convenient way is to have dedicated binaries - thus a rename is needed. Just renaming kwin for wayland is also not a good idea as in future the "main" kwin will be for wayland not for X11. Another case for the dedicated binaries is the Application class, which right now first tries to claim the X11 Window Manager Selection. Again on Wayland even with XWayland we won't need that. KWin will be the window manager for XWayland if KWin is the Wayland compositor. There is no need to even try to support anything else. Most likely it will even be KWin to start the XWayland server, so we can be sure that there is no other WM running and thus no need to claim the selection and abort if it fails. REVIEW: 118266
2014-06-10 14:05:54 +04:00
#define KWIN_INTERNAL_NAME_X11 "${KWIN_INTERNAL_NAME_X11}"
Add CMake variable to rename kwin binaries A CMake variable is used to specify the name of the binary. By default this is "kwin" but building for PA changes the name to "kwinactive". The variable adjusts all names, e.g. kwinnvidiahack becomes kwinactivenvidiahack. The remaining usage of kwinrc in core and libs is replaced by a cmakedefine for the configuration name and all data installations are moved to the defined name. Dynamic loading for scripts & co is adjusted for loading based on defined name. This change allows the side-by-side installation of both kwin for desktop and kwin for Plasma Desktop without the known issues like conflicts in config files or missing build options if kwin desktop is used for Plasma Active. Likewise the KCMs are not adjusted as they are not intended to be used for kwinactive. REVIEW: 104299 BUG: 296084 FIXED-IN: 4.9.0 CCMAIL: active@kde.org
2012-03-16 11:37:09 +04:00
#define KWIN_CONFIG "${KWIN_NAME}rc"
use standard way to version applications in Plasma
2014-08-20 17:43:27 +04:00
#define KWIN_VERSION_STRING "${PROJECT_VERSION}"
Add Qt and XCB compile version to supportInformation Add QT_VERSION_STR in addition to qVersion(). This could be useful to see whether the runtime version is different to the Qt version used at compile time. Also adds the XCB_VERSION_STRING which is used at compile time. This is useful as for example XCB::SYNC was broken prior to 1.10. REVIEW: 122375
2015-02-02 11:28:14 +03:00
#define XCB_VERSION_STRING "${XCB_VERSION}"
Fix invocation of kwin_killer_helper Path needs to be hard coded as it's in libexec. REVIEW: 117999
2014-05-05 19:10:22 +04:00
#define KWIN_KILLER_BIN "${CMAKE_INSTALL_PREFIX}/${LIBEXEC_INSTALL_DIR}/kwin_killer_helper"
[kwin] Fix ifdefs for Wayland With the switch to FindWayland from ECM WAYLAND_FOUND was no longer set thus the ifdef didn't work. Now we use HAVE_WAYLAND and HAVE_WAYLAND_EGL.
2014-03-13 19:21:04 +04:00
#cmakedefine01 HAVE_WAYLAND
#cmakedefine01 HAVE_WAYLAND_EGL
[wayland] Make Wayland::Cursor a proper optional build dep Only needed in the Wayland backend and can easily be ifdefed there.
2015-03-23 12:07:59 +03:00
#cmakedefine01 HAVE_WAYLAND_CURSOR
InputRedirection for keyboard events Major new functionality is xkbcommon support. InputRedirection holds an instance to a small wrapper class which has the xkb context, keymap and state. The keymap is initialied from the file descriptor we get from the Wayland backend. InputRedirection uses this to translate the keycodes into keysymbols and to QString and to track the modifiers as provided by the Qt::KeybordModifiers flags. This provides us enough information for internal usage (e.g. pass through effects if they have "grabbed" the keyboard). If KWin doesn't filter out the key events, it passes them on to the currently active Client respectively an unmanaged on top of the stack. This needs still some improvement (not each unmanaged should get the event). The Client/Unmnaged still uses xtest extension to send the key events to the window. So keylogging is still possible.
2013-07-02 13:44:18 +04:00
#cmakedefine01 HAVE_XKB
Initial support for libinput Libinput is an optional dependency for getting low level input events. As opening the input devices requires root privs this is rather pointless in the current state. But there is a small added test app which can be executed with root privs to demonstrate the functionality. To properly get input events we need a wrapper like it's used in weston. So far the following is setup: * opening devices found by udev * forwarding keyboard events to InputRedirection * forwarding pointer button events to InputRedirection * forwarding pointer axis events to InputRedirection * signals emitted for pointer motion events Pointer motion events need some further work as they are provided as delta events. We need to track that and map them properly. Also missing are touch events due to me not having a touch screen. It should be fairly simple to setup the touch events, though. Also hotplugging of devices is not yet implemented.
2014-08-14 16:43:57 +04:00
#cmakedefine01 HAVE_INPUT
Use xcb_cursor library instead of Xlib based one in Cursor Straight forward port from XLib based XCursor library to the xcb variant which is considerably new. The xcb variant only allows to create xcb_cursor_t for the default theme and size. Which suits the needs in Cursor quite well, but means it's not a replacement for the usage in zoom effect. REVIEW: 122290
2015-01-28 16:49:27 +03:00
#cmakedefine01 HAVE_XCB_CURSOR
Switch to xcb for sync extension Since XCB 1.10 the sync extension is working properly. At the time of the 5.3 release 1.10 will have been out for ~15 months, enough time for distros to catch up and should allow us to use it. As our CI system only supports 1.9 at the moment we cannot hard depend on the version, instead we use feature info. As soon as our CI system supports it, we should update the required min version and kick out the ifdef. REVIEW: 122377
2015-02-02 12:07:10 +03:00
#cmakedefine01 HAVE_XCB_SYNC
[wayland] Create xcb_connection through XLib in windowed mode Adds optional dependency to X11_XCB and gets used in X11WindowedBackend to create an XLib Display if dependency is present. This allows to create an EGL backend for the X11WindowedBackend.
2015-03-19 13:07:49 +03:00
#cmakedefine01 HAVE_X11_XCB
[kwin] Add used features from config-workspace.h to config-kwin.h Adds HAVE_UNISTD_H and HAVE_MALLOC_H to config-kwin.h and gets used in main.cpp. With that KWin does no longer need config-workspace.h.
2014-03-18 12:30:40 +04:00
/* Define to 1 if you have the <unistd.h> header file. */
#cmakedefine HAVE_UNISTD_H 1
/* Define to 1 if you have the <malloc.h> header file. */
#cmakedefine HAVE_MALLOC_H 1
Make xcb-icccm truely optional ICCCM dependency is a beast due to two different existing versions in different packages. Thus it cannot be a hard dep without causing problems for our downstreams. This change ensures that ICCCM is really considered as an optional dep and that the version we need is found, if not we mark it as non-found. ICCCM is only used by one test application which can easily be disabled and some enum values are used in events.cpp. If ICCCM is not found those are replaced by defines generated in config-kwin.h. BUG: 336035
2014-06-11 09:51:07 +04:00
#cmakedefine XCB_ICCCM_FOUND 1
#ifndef XCB_ICCCM_FOUND
#define XCB_ICCCM_WM_STATE_WITHDRAWN 0
#define XCB_ICCCM_WM_STATE_NORMAL 1
#define XCB_ICCCM_WM_STATE_ICONIC 3
#endif