Age | Commit message (Collapse) | Author | Files | Lines |
|
Changes:
- Remove the autobuild scripts and config.xml used by the app
framework widget build.
- Update the CMake files to just build a "xdg-cluster-receiver"
binary and install it into /usr/bin by default.
- Bumped agl-compositor protocols version requirement to 0.0.20 to
work with current AGL.
- Remove the code in main.cpp that handled reading the WebSocket
command-line arguments and passing them to binding related
code.
Bug-AGL: SPEC-4283
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: I8c9bd3af9ce16f29f24282b89985c0d4d5d9c922
|
|
This has run-by-default enabled.
Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
Change-Id: I99c85373965339a990476eec1772a27cfd360d6c
|
|
Update the autobuild script and CMake files to work with the SDK, and
remove now deprecated usage of the app-templates submodule.
Bug-AGL: SPEC-3055
Change-Id: I720f4d530dbd749e8426b3f12d04ad2b34d700d4
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
|
|
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>
|