| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
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
|
|
We did use the variable AGL_APP_REVISION to change between the HEAD of the branch
via to the fixed tag at release time (regs/tags/xyz) .
While this worked well previously, it turns out that bitbake will query git every time
it runs for either or tags likewise. For tags it cannot trust whatever is known locally
is actually the latest tags as there can be force pushed tags.
To fix this we use a well-defined SRCREV for apps/* in the same way
as we do it for src/* .
Bug-AGL: SPEC-4455
Signed-off-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
Change-Id: I97fc125d40b36b7ac5e069018a8973384f61d0b7
|
|
Changes:
- Restore the image recipes for the agl-cluster-demo-platform and
agl-telematics-demo-platform images, with updates to them and
their associated packagegroups for the app framework removal.
- Restore updated recipes required for the above, including:
* cluster-dashboard
* cluster-receiver
* qt-cluster-receiver
* tbtnavi
- Simple systemd unit files have been added for the cluster
applications and are installed as user session units. Starting
of cluster-dashboard (the XDG version) and cluster-receiver in
the AGL user session is enabled by default.
- The recipes to install the dedicated network configuration for
the cluster demo have been restored so that the
agl-cluster-demo-support and agl-demo-preload features will do
what is expected again.
Known outstanding issues:
- The previous signal-composer binding support has been removed
from cluster-dashboard, so related functionality (i.e. driving
it from CAN) is disabled until replacement is worked out.
- While tbtnavi builds, the previous use of the navigation binding
is stubbed out in libqtappfw, so it will not receive location
and route information from ondemandnavi.
- Nothing has been added yet to start tbtnavi in the AGL user
session, the plan is to do so with a systemd user unit once a
new mechanism for controlling it from ondemandnavi has been
implemented.
- The telematics-recorder application has not yet been updated
to replace its signal-composer, gps, and network binding use.
The intent is to address these issues in the 13.0.x point releases.
Bug-AGL: SPEC-4283
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: I520c23775b21504cb7dd92538319cc5bf826ff64
|
|
During the last workshop the transition to the new framework was presented.
This change essentially deprecates the SMACK-based application framework.
To prepare the integration of it, we remove the deprecated components:
- recipes-apis : all agl-service-*
- recipes-demos: all demo apps but homescreen
- non-essential configurations
Todo:
We need to bring-back the html5 image in a follow-up w/o ties into the old framework.
v2: kept WAM + Chromium recipes for reference
v3: rebased
Bug-AGL: SPEC-4121
Signed-off-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
Change-Id: I58075f5f1e477106a1aad3d2171a0904bf0cb16e
|
|
This is the result of running a slightly customized version of the
convert-overrides.py script from poky with additional overrides
added.
The intent of these changes is to minimize the effort to keep the
"next" branch that builds against poky master up to date and tested
in preparation for the switch to the next Yocto LTS release in
early 2022.
Bug-AGL: SPEC-4052
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: I6eeadd2c985c008b04f8f9815bf0f6fb064bedac
|
|
Update runtime dependencies in demo app recipes to match current
binding requirements.
Bug-AGL: SPEC-3748
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: Ibaab8d0d2b00f764946ed8472e76a504647b697e
|
|
Update demo app recipes as appropriate to remove now unused build
dependencies such as libhomescreen, qlibhomescreen, and qtwebsockets.
Bug-AGL: SPEC-3748
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: Ic3b17bf868dcd0ad633bd09f53311e11ec0a1a00
|
|
Update spacing and variable ordering in the demo app recipes for
consistency per the OpenEmbedded syle guide (see:
https://www.openembedded.org/wiki/Styleguide). Additionally,
a common cut-and-pasted unnecessary comment has been removed from
the recipes. There are no functional changes.
Bug-AGL: SPEC-3748
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: Ic7cf3a1392678e76e8f512acb4f16b623fa35d3f
|
|
All demo related components should be in here now.
We keep the packagegroups on purpose for now to stay backward-compatible.
v2: layer does pass yocto-check-layer, dependencies adapted
v3: remove the dynamic-layer setup, use all-in-one approach
v4: Fixed comments from Paul Barker. Tnx!
v5: Removed wayland/weston/agl-compositor additions, except for demo
specific weston-init bbappend
Follow-up changes required later:
- massaging packagegroups
- scrub of recipes
Bug-AGL: SPEC-3723
Signed-off-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: I47cefd8c23d46b2cdd063470e3f7d97d5ad952d8
|
Scott Murray
Jan-Simon Moeller