| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Changes to switch the Qt-based agl-demo-platform demo from using
the older KUKSA.val server to the new gRPC based databroker. The
Flutter demo's vehicle signalling behavior ends up a bit broken
by these, but the image still boots and basic things still work.
A follow on set of changes will convert the Flutter apps to the
new gRPC API and remove the KUKSA.val server completely.
Notable changes:
- Updated libqtappfw, homescreen, ondemandnavi, and tbtnavi recipes
to pick up changes to switch to using the databroker.
- Updated agl-service-audiomixer and agl-service-hvac recipes to
pick up their rework for using the databroker.
- All the Qt demo applications that use the VehicleSignals class
from libqtappfw have had their .conf and .token files updated to
work with the databroker. As well, the JSON files used to create
the new app-specific authorization tokens have been checked in to
provide a reference of how things are configured.
- The DBC feeder configuration has been changed to push into the
databroker. Having a duplicate instance to also push into the
older server has not been set up, as hopefully the Flutter demo
conversion will follow on quickly enough to not require it.
- Packagegroups for the KUKSA.val server and databroker have been
factored out and are used instead of using the agl-ivi-services
packagegroup.
- kuksa-databroker-cli and the simple CAN simulator script are now
included into the demo images when building with agl-devel.
Bug-AGL: SPEC-4762
Change-Id: I416bcfbf961535062043ef54acdea6c353f84af1
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl-demo/+/29171
Tested-by: Jenkins Job builder account
ci-image-build: Jenkins Job builder account
ci-image-boot-test: Jenkins Job builder account
Reviewed-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
|
|
While the change to ensure polkit starts before applaunchd in
meta-app-framework should resolve the observed failures, it is also
the case that the applications here that call into the applaunchd
API did not have dependencies on it in their systemd units, so also
fix that to improve overall robustness.
Bug-AGL: SPEC-4840
Change-Id: I884b7b326309a0dbdc374a93929aa33f421c680c
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
|
|
Remove the use of systemd user session to align with how upstream
runs Weston, and to allow using all systemd sandboxing features with
the compositor and homescreen, launcher, etc. applications. The
changes for this touched enough packagegroups and images that further
rework was done to address some of the cleanup described in SPEC-4813,
see below for details.
Changes:
- Rework systemd units and recipes of affected applications.
- Rework images to pull in image .bb files instead of .inc files.
- Pull in the new agl-image-compositor as a base image where
appropriate.
- Update weston-terminal-conf recipe to use new split out
weston-terminal package.
- Use new agl-crosssdk bbclass where appropriate.
- Pull some local common cross-SDK additions into a new
agl-ivi-crosssdk.inc include file and use as appropriate. Note
that this does have a side effect of likely correcting the contents
of agl-image-ivi-crosssdk for some recent additions.
- Remove flutter-gallery bbappend that turned it into an app, as we
are not using it in images, have other examples now, and it seems
better to not affect the contents of agl-image-flutter.
- Remove unused agl-image-graphical-html5. If a downstream user does
desire an image with Chromium+WAM without applications, restoring it
can be considered.
- Remove unused agl-image-graphical-qt5-crosssdk.
- Remove all packagegroup-agl-profile-* packagegroups, as they were
either empty or not providing value at this point. Any future plans
for defining profiles can start from a clean sheet.
- Added new packagegroup-agl-ivi-multimedia-hardware to hold some
rcar3 specific additions (via override) that were previously being
appended onto packagegroup-agl-graphical-multimedia even though
they are machine-specific and that packagegroup is not. This may
be a stopgap solution if the agl-ivi-* packagegroups are reworked
further.
- Replace some :append usage with += to avoid creating problems
for downstream users.
Bug-AGL: SPEC-4714, SPEC-4813
Change-Id: I544b1495bed1e2e2412a8e46b7d20d7622ec28c9
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
|
|
Update the recipes for the Qt demo applications that were previously
using signal-composer either directly or indirectly to work with the
new VehicleSignals API in libqtappfw. For most of them this means
updating their SRCREV to pick up the application changes, and
installing the new configuration file and associated JSON web token
file for KUKSA.val authorization. At present all the apps are using
one of the default read-write tokens from the KUKSA.val install, but
ideally this will end up migrated to app specific tokens with
appropriate permissions JSON down the road, potentially obtained
via OAuth or similar mechanism.
Additionally, the tbtnavi recipe has been updated to install a
systemd unit to start it at boot.
Bug-AGL: SPEC-4409, SPEC-4426
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: I46be098fc31be02852e7888ba0ffd14674efa12b
|
|
`homescreen` relies on `/etc/default/homescreen` to contain its
environment variables, however this feature was lost when we switched
to systemd services.
This commit restores this feature by instructing systemd to source
`/etc/default/homescreen` if it exists.
Bug-AGL: SPEC-4161
Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>
Change-Id: I62c8597eac7d14d9d5166f9c559a1538398cd0c8
|
|
Bug-AGL: SPEC-4161
Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>
Change-Id: I3f53c4d9143baad15fee59110f5f9fbf64290d6c
|
|
Rework homescreen demo app recipe for building a version of it
with the application framework usage removed. A simple systemd
unit to start it has been added as a placeholder until the new
application scheme has been added. This will at least produce
something on screen for testing, and the HOMESCREEN_DEMO_CI
environment variable can be defined via /etc/default/homescreen
to potentially re-enable the CI startup test.
Bug-AGL: SPEC-4121
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: I510873d428dc98286775722e23b34cd4a9862258
|
Scott Murray
Arnaud Ferraris