summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
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 Murray15-0/+980
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>
2018-11-26Initial empty repositoryguppy_6.99.2guppy/6.99.26.99.2Jan-Simon Moeller0-0/+0