summaryrefslogtreecommitdiffstats
path: root/app
AgeCommit message (Collapse)AuthorFilesLines
2021-07-01CMakeLists.txt: Use pkg-config to retrieve the protocols pathmarlin_12.92.0marlin_12.91.0marlin_12.90.1marlin/12.92.0marlin/12.91.0marlin/12.90.112.92.012.91.012.90.1Marius Vlad1-6/+10
Bug-AGL: SPEC-3423 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I380bfc5f53fabe83ebf71648cf6d4effc31d44ad
2020-07-14Rip out the qt version and intall the native XDG onejellyfish_9.99.2jellyfish/9.99.29.99.2Marius Vlad8-642/+825
This has run-by-default enabled. Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I99c85373965339a990476eec1772a27cfd360d6c
2020-07-10app: Use waylandsink for all platformsMarius Vlad1-25/+4
Bug-AGL: SPEC-3382 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I7bbb34a377921bc5f741495f14951a0df70694cb
2020-07-10Conversion to using agl-compositorMarius Vlad7-216/+683
- Use Qt/QtWayland to set-up an app_id for the main surface. We use that surface and pass it to waylandsink. Waylandsink create a sub-surface with the parent the Qt/QtWayland one. - Install a handler for handling bus messages With it, it allows to pass the wl_display with the help of a context and the surface backing up the Widget. - Installs a timer to wait for Qt to create/get the xdg_surface and attach a buffer to it. Without we won't be able receive the commit for the parent event in order to handle it. Bug-AGL: SPEC-3382 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I4237b7dad110ce36e3a01226e67cb508b6d9a6d9
2019-06-12Update to apply remoting pluginhalibut_7.99.2halibut/7.99.27.99.2Harunobu Kurokawa1-2/+2
Remoting plugin uses jpeg element as default. This pipeline is refered from sample script in https://gitlab.freedesktop.org/wayland/weston/blob/master/doc/remoting-client-receive.bash Bug-AGL : SPEC-2420 Signed-off-by: Harunobu Kurokawa <harunobu.kurokawa.dn@renesas.com> Change-Id: I83e3bf9e75af24d80993ed1ef78c01154ae94c1b
2019-04-23Fix compilation against newer Wayland IVI extensionhalibut_7.99.1halibut/7.99.17.99.1Scott Murray1-3/+3
The ilm_init function has moved to the new libilmCommon library in Wayland IVI extension 2.x, so switch to using the ilmCommon package config in the application CMakeLists.txt. ilmCommon has a dependency on ilmControl, so that still gets pulled in. Change-Id: Id9cefd7cb1ceec826d44011d91ad1f196e7e19b2 Signed-off-by: Scott Murray <scott.murray@konsulko.com>
2019-03-26Add waylandsink fallbackScott Murray1-1/+22
Add a check for vaapisink availability, and fall back to using waylandsink if it is unavailable. This should allow using a non-Intel board for the cluster demo, though there are potentially issues around having a H.264 decoder plugin available that may need to be addressed in the target platform BSP (e.g. Raspberry Pi). Change-Id: Ie351fe0cd6e36e3db6707b9202b3b1fd7c66d3ce Signed-off-by: Scott Murray <scott.murray@konsulko.com>
2018-12-04Initial check-inhalibut_7.90.0halibut/7.90.0guppy_6.99.4guppy_6.99.3guppy/6.99.4guppy/6.99.37.90.06.99.46.99.3Scott Murray5-0/+543
Demo instrument cluster receiver application to receive a h264 stream sent via RTP from another host running Wayland and Weston with the gst-recorder feature for streaming a virtual display patched in. The gstreamer pipeline used is based on what was being used with gst-launch-1.0 in the previously hand-constructed instrument cluster demo. The use of vaapisink likely constrains use to Intel based platforms at present, future work should allow working on other platforms. The app/surface.{hpp,cpp} files are adapted from code from xdg-launcher: https://gerrit.automotivelinux.org/gerrit/staging/xdg-launcher Note that they are MIT licensed while all other source files are Apache 2.0. Other than significant refactoring to ease integration, the functional differences from the runxdg code in xdg-launcher are that homescreen support has been removed, as the instrument cluster platform does not use it, and the logging has been reworked to use the hmi-debug mechanism used by the windowmanager and homescreen. There is also an implicit assumption that the windowmanager configuration is such that the "app" role will map the receiver's surface to the desired location in the center of the dashboard. Change-Id: Ieddef6463efb744d9c9c28b1508cc930a32981a4 Signed-off-by: Scott Murray <scott.murray@konsulko.com>