summaryrefslogtreecommitdiffstats
path: root/src/plugins/shellintegration/ivi-shell/ivi-shell.pro
diff options
context:
space:
mode:
authorYusuke Binsaki <yusuke.binsaki@itage.co.jp>2016-02-10 18:52:59 +0900
committerYusuke Binsaki <yusuke.binsaki@itage.co.jp>2016-02-12 21:29:13 +0000
commitf144f0f71f1b75df9216c36747513444c7941c09 (patch)
tree4e2db8eed7c4f915fb8ed51a7e8c583bf442f456 /src/plugins/shellintegration/ivi-shell/ivi-shell.pro
parent74b1ec474d1d48242893dcaf58b8a35f155f3fc3 (diff)
Implement initial IVI-shell support with shell integration.
IVI-shell provides a shell interface for Weston, which maps the GENIVI API (http://www.genivi.org) for In-Vehicle Infotainment as Wayland-Ivi-Extension (http://wiki.projects.genivi.org/index.php/Wayland_IVI_Extension_Design). This patch is included in two protocol. The first is ivi-application protocol which provided by weston. Next is ivi-controller protocol which provided by Genivi's wayland-ivi-extension. In IVI use case, the client create and destroy surface with the unique ID by using ivi-application protocol. On the other hand, the controller such as HMI Controller control some properties, which are visibility, position, size, etc, with created the unique ID by using ivi-controller protocol. It means the unique ID is necessary to create and control the ivi-surface and the the ivi-layer. However Qt has no API to set the some surface or layer ID. In this ivi-shell plugin, the unique ID can be set via the environment parameter so that we can control the ivi-surface and ivi-layer. The name of environment parameter is QT_IVI_SURFACE_ID. QT_IVI_SURFACE_ID will be used as ivi-surface and ivi-layer. If application needs more than two surfaces, ivi-surface IDs will be incremented. When QT_IVI_SURFACE_ID isn't set, ivi-surface and ivi-layer ID will be generated internally. The ID consists of the process ID and the surface ID which is incremented in ivi-shell plugin. The process ID is used as lower 22 bit per 32bit. 23 to 32 bit is used as the surface IDs in a process. e.g. When the process ID is 0x765 and create two surfaces, ivi-layer ID is 0x765 and ivi-surface IDs are 0x765 and 0x00400765. +------------+---------------------------+ |31 23|22 0| +------------+---------------------------+ |0000 0000 00|00 0000 0000 0000 0000 0000| |<- ID ->|<- process ID ->| +------------+---------------------------+ We can set QT_WAYLAND_SHELL_INTEGRATION of the environment parameter to "ivi-shell" to use IVI-shell. Change-Id: Iddcfb3de89dc022530c0285524cf6bbf640147b6 Reviewed-by: Giulio Camuffo <giuliocamuffo@gmail.com>
Diffstat (limited to 'src/plugins/shellintegration/ivi-shell/ivi-shell.pro')
-rw-r--r--src/plugins/shellintegration/ivi-shell/ivi-shell.pro38
1 files changed, 38 insertions, 0 deletions
diff --git a/src/plugins/shellintegration/ivi-shell/ivi-shell.pro b/src/plugins/shellintegration/ivi-shell/ivi-shell.pro
new file mode 100644
index 000000000..8fd774736
--- /dev/null
+++ b/src/plugins/shellintegration/ivi-shell/ivi-shell.pro
@@ -0,0 +1,38 @@
+PLUGIN_TYPE = wayland-shell-integration
+load(qt_plugin)
+
+QT += waylandclient-private
+CONFIG += wayland-scanner
+
+!contains(QT_CONFIG, no-pkg-config) {
+ PKGCONFIG += wayland-client wayland-cursor
+ CONFIG += link_pkgconfig
+} else {
+ LIBS += -lwayland-client -lwayland-cursor
+}
+
+config_xkbcommon {
+ !contains(QT_CONFIG, no-pkg-config) {
+ PKGCONFIG += xkbcommon
+ } else {
+ LIBS += -lxkbcommon
+ }
+} else {
+ DEFINES += QT_NO_WAYLAND_XKB
+}
+
+WAYLANDCLIENTSOURCES += \
+ ../../../3rdparty/protocol/ivi-application.xml \
+ ../../../3rdparty/protocol/ivi-controller.xml
+
+HEADERS += \
+ qwaylandivishellintegration.h \
+ qwaylandivisurface_p.h
+
+SOURCES += \
+ main.cpp \
+ qwaylandivishellintegration.cpp \
+ qwaylandivisurface.cpp
+
+OTHER_FILES += \
+ ivi-shell.json