| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Explicitly add kuksa-certificates-ca-agl to the cluster demo images so
it will be included in both regular and agl-demo-preload builds. Also
remove obsolete dependency on kuksa-certificates-client-agl from the
cluster-dashboard recipe, and kuksa-databroker RRECOMMENDS from the
libqtappfw recipe to fix the regular vs agl-demo-preload behavior for
the agl-cluster-demo-platform build.
Bug-AGL: SPEC-4986
Change-Id: I62b1d976c66824fde50a3effdcdd34b428e82d54
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl-demo/+/29472
ci-image-build: Jenkins Job builder account
Reviewed-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
ci-image-boot-test: Jenkins Job builder account
Tested-by: Jenkins Job builder account
|
|
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>
|
|
Changes:
- Tweak the kuksa-val recipe to remove installing a newer server
certificate (since it will be done elsewhere), and to split the
certificates up into finer grained packages to ease installing
them piecemeal and replacing them with other packages.
- Remove the unused genCerts.sh certificate script patch form the
kuksa-val recipe, an updated patch will be added in the near
future.
- Added a patch in the kuksa-viss-client recipe that enables the
library to use certificates installed in /etc/kuksa-certificates or
/etc/kuksa-val instead of the default ones that are shipped.
- Add kuksa-certificates-agl recipe that installs AGL specific CA,
server, and client certificates plus the required server and client
keys to act as a replacement for the default ones shipped with
KUKSA.val. The kuksa-certificates-agl name is used to avoid needing
a rename with a future switch to kuksa-databroker. Note that the
RPROVIDES variable is used for the various certificate packages to
make them installable alternatives to the kuksa-val-certificates-*
ones. The certificates installed are valid for 1 year and have
AGL as the providing organization, longer validity ones will be
added in follow up commits for Octopus and Pike.
- Update the existing users of kuksa-val-*-certificates with the new
kuksa-val-certificates-* package names.
- Add PREFERRED_RPROVIDER definitions for the kuksa-val-certificates-*
packages to quiet the BitBake warnings coming from having multiple
providers.
Bug-AGL: SPEC-4763
Change-Id: Ic6f1ca8b54f637674cd5ae42df0bed6ca4e729aa
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
|
|
Add CLUSTER_DEMO_VISS_HOSTNAME variables to the cluster-dashboard
and flutter-cluster-dashboard recipes and tweak the installed
configuration files to use the address it specifies. This provides
a hook for tweaking the configuration for e.g. running in the guest
VMs in the QEMU+KVM demo. This may need to be tweaked down the
road to use something like multiple packages + the alternatives
mechanism instead.
Bug-AGL: SPEC-4618
Change-Id: I3798987566d681eac59e8c4b9c1f2423d950b2ba
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
(cherry picked from commit 5109016c566a4a46e4a85f2c7b9dfcd6b8540233)
|
|
Update SRCREVs for the agl-service-audiomixer and agl-service-hvac
services as well as the dashboard and agl-cluster-demo-dashboard apps
to pick up fixes for signal changes in KUKSA.val 0.2.5.
Bug-AGL: SPEC-4587, SPEC-4598
Change-Id: I581ad6560032c76458e00658b750cba7d0b6e1de
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
|
|
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:
- Update "BSD" license declaration in cluster-gauges-qtcompositor
and cluster-dasboard recipes to now required more specific
"BSD-3-Clause" after checking in the source tree.
- Make packagegroup-agl-profile-cluster-qtcompositor machine-specific
to avoid tripping the new check for depending on dynamically renamed
packages.
Bug-AGL: SPEC-3819
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: I24915cd85cb3854b3f9bc7947adda9cb5d42d8a9
|
|
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 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
|
|
Replace remaining now unnecessary gitsm fetcher usage with just
plain git.
Bug-AGL: SPEC-3748
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: Ic6913eb833ea3a8166db02064828f737da49cf92
|
|
Update the SUMMARY and DESCRIPTION variable definitions in the
various demo application recipes to remove old references to
"CES 2017" and make them more consistent.
Bug-AGL: SPEC-3748
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: I97cc00610463aa59f7e23ecccc9c625fbfed7a74
|
|
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