## Introduction
-The `meta-agl-demo` layer is the IVI demo layer that uses the core
-AGL infrastructure provided through profiles.
-The layer sits on top of the profiles as follows:
-
-profile-core <- profile-gfx <- profile-gfx-qt5
-
+The `meta-agl-demo` layer is the reference user interface layer for the DEMO
+platform of Automotive Grade Linux (AGL).
The layer provides a reference platform and applications.
-The BitBake target name for the demo platform is `agl-demo-platform`,
-which is the full demo platform image.
+The BitBake target name for the DEMO platform is `agl-demo-platform`, which is
+the full DEMO platform image.
## Layer Dependencies
* Yocto Project Release:
- URI: git://git.yoctoproject.org/poky
- - Branch: "thud"
+ - Branch: "dunfell"
- Tested Revision: See the [`default.xml`](https://github.com/leon-anavi/AGL-repo/blob/master/default.xml)
manifest file for the `AGL-repo` repository for revision
- information.
+ information.<br/><br/>
* AGL `meta-agl` Layer:
- URI: https://gerrit.automotivelinux.org/gerrit/AGL/meta-agl
- - Branch: "flounder"
+ - Branch: "master"<br/><br/>
* OpenEmbedded `meta-openembedded` Layer:
manifest file for the `AGL-repo` repository for revision
information.
- Specifically, out of `meta-openembedded`, these sub-layers are used:
+ Specifically, out of `meta-openembedded`, these sub-layers are used:
- - `meta-oe`
- - `meta-multimedia`
- - `meta-efl`
- - `meta-networking`
- - `meta-python`
- - `meta-ruby`
+ - `meta-oe`
+ - `meta-multimedia`
+ - `meta-networking`
+ - `meta-python`<br/><br/>
-* Yocto Project `meta-qt5` Layer from the
+* Yocto Project `meta-qt5` Layer from the
[OpenEmbedded Layer Index](https://layers.openembedded.org/layerindex/branch/master/layers/):
- URI: https://github.com/meta-qt5/meta-qt5.git
- - Branch: "thud"
+ - Branch: "dunfell"
- Tested Revision: See the [`default.xml`](https://github.com/leon-anavi/AGL-repo/blob/master/default.xml)
manifest file for the `AGL-repo` repository for revision
- information.
+ information.<br/><br/>
+
### Feature Dependencies
The `meta-agl-demo` layer has the following AGL
-[feature](../../../../getting_started/en/dev/reference/image-workflow-initialize-build-environment.html#agl-features)
+[feature](../getting_started/reference/getting-started/image-workflow-initialize-build-environment.html#agl-features)
dependencies:
-**The `agl-appfw-smack` Feature:**
-
-<!--
-* Yocto Project `meta-intel-iot-security` Layer from the OpenEmbedded Layer Index:
-
- - URI: https://github.com/01org/meta-intel-iot-security
- - Branch: "thud"
- - Tested Revision: See the [`default.xml`](https://github.com/leon-anavi/AGL-repo/blob/master/default.xml)
- manifest file for the `AGL-repo` repository for revision
- information.
--->
-
* Yocto Project `meta-security` Layer:
- URI: https://git.yoctoproject.org/cgit/cgit.cgi/meta-security
- Branch: "master"
- Tested Revision: See the [`default.xml`](https://github.com/leon-anavi/AGL-repo/blob/master/default.xml)
manifest file for the `AGL-repo` repository for revision
- information.
+ information.<br/><br/>
-* AGL's `meta-app-framework` Layer Within the `meta-agl-extra` Layer:
+* AGL's `meta-app-framework` Layer within the `meta-agl` Layer:
- - URI: https://gerrit.automotivelinux.org/gerrit/gitweb?p=AGL/meta-agl-extra.git
- - Branch: "master"
+ - URI: https://gerrit.automotivelinux.org/gerrit/gitweb?p=AGL/meta-agl.git
+ - Branch: "master"<br/><br/>
**The `agl-sota` Feature:**
-* AGL's `meta-sota` Layer Within the `meta-agl-extra` Layer:
+* Here Technologies' `meta-updater` Layer:
- - URI: https://gerrit.automotivelinux.org/gerrit/gitweb?p=AGL/meta-agl-extra.git
- - Branch: "master"
+ - URI: https://github.com/advancedtelematic/meta-updater/
+ - Branch: "dunfell"<br/><br/>
+
+* Here Technologies' `meta-updater-qemux86-64` Layer:
+
+ - URI: https://github.com/advancedtelematic/meta-updater-qemux86-64/
+ - Branch: "dunfell"<br/><br/>
* OpenEmbedded's `meta-openembedded` Layer:
- URI: https://github.com/openembedded/meta-openembedded
- - Branch: "thud"
+ - Branch: "dunfell"
- Tested Revision: See the [`default.xml`](https://github.com/leon-anavi/AGL-repo/blob/master/default.xml)
manifest file for the `AGL-repo` repository for revision
information.
- In particular, the `meta-openembedded` layer depends on the following
- sub-layers:
-
- - `meta-filesystems`
- - `meta-ruby`
+ Specifically, out of `meta-openembedded`, these sub-layers are used:
-<!--
-* OpenEmbedded's `meta-rust` Layer:
-
- - URI: https://github.com/meta-rust/meta-rust
- - Branch: "thud"
- - Tested Revision: See the `[default.xml](https://github.com/leon-anavi/AGL-repo/blob/master/default.xml)`
- manifest file for the `AGL-repo` repository for revision
- information.
--->
+ - `meta-filesystems`
+ - `meta-oe`
+ - `meta-python`<br/><br/>
**The `agl-netboot` Feature:**
-* AGL's `meta-netboot` Layer Within the `meta-agl` Layer:
+* AGL's `meta-netboot` Layer within the `meta-agl` Layer:
- URI: https://gerrit.automotivelinux.org/gerrit/gitweb?p=AGL/meta-agl.git
- Branch: "master"
+## Maintenance
-## Packagegroups
-
-AGL DEMO Platform's
-[packagegroups](https://www.yoctoproject.org/docs/2.4.4/dev-manual/dev-manual.html#usingpoky-extend-customimage-customtasks)
-consist of the following:
-
-### packagegroup-agl-demo-platform
-
-This packagegroup is used for generating the `agl-demo-platform` image,
-which is the full image for the AGL distributions IVI profile.
-You can see the recipe (i.e. `agl-demo-platform.bb`) that installs
-the `packagegroup-agl-demo-platform` packagegroup
-[here](https://git.automotivelinux.org/AGL/meta-agl-demo/tree/recipes-platform/images/agl-demo-platform.bb).
-
-As meta-agl's design of packagegroups, the `agl-demo-platform.bb` recipe installs
-the `packagegroup-agl-demo-platform` packagegroup, which pulls in the following
-packages of the DEMO applications:
-
- * `agl-demo-platform`
- * `packagegroup-agl-image-minimal`
- * `packagegroup-agl-image-ivi`
- * `packagegroup-ivi-common-core`
- * `packagegroup-agl-demo-platform`
-
-<!--
-### packagegroup-agl-appfw*
-
-These packagegroups contain packages for the AGL distribution's
-Application Framework.
-Subsystem should maintain `packagegroup-agl-appfw-[subsystem].bb`, which
-should hold sufficient packages for the Application Framework.
-
-Subsystems also can maintain their own packagegroups using appropriate
-`recipes-*/`.
-For example, Qt5 has two packagegroups in `meta-agl-demo`:
-`packagegroup-agl-appfw-native-qt5` and `packagegroup-agl-demo-qt-examples`,
-which are under `recipes-qt/`.
+All patches must be submitted via the AGL Gerrit instance at
+<https://gerrit.automotivelinux.org>. See this wiki page for
+details:
-The `packagegroup-agl-appfw-native-qt5` is included by
-`packagegroup-agl-appfw-native` because Qt5 belongs to native application
-framework of AGL Distro.
+<https://wiki.automotivelinux.org/agl-distro/contributing>
-Because the `packagegroup-agl-demo-qt-examples` is not mandatory for
-the AGL Application Framework and the AGL DEMO, the packagegroup is added
-to the layer's `local.conf` file only when needed.
--->
+Layer maintainers:
+* Jan-Simon Möller <jsmoeller@linuxfoundation.org>
Code Review / AGL / meta-agl-demo.git / blobdiff