3 The `meta-agl-demo` layer is the reference user interface layer for the DEMO
4 platform of Automotive Grade Linux (AGL).
5 The layer provides a reference platform and applications.
6 The BitBake target name for the DEMO platform is `agl-demo-platform`, which is
7 the full DEMO platform image.
11 This section describes dependencies for the `meta-agl-demo` layer.
12 Dependencies are grouped into base, hardware, and feature dependencies.
16 The `meta-agl-demo` layer has the following base dependencies:
18 * Yocto Project Release:
20 - URI: git://git.yoctoproject.org/poky
22 - Tested Revision: See the [`default.xml`](https://github.com/leon-anavi/AGL-repo/blob/master/default.xml)
23 manifest file for the `AGL-repo` repository for revision
24 information.<br/><br/>
26 * AGL `meta-agl` Layer:
28 - URI: https://gerrit.automotivelinux.org/gerrit/AGL/meta-agl
29 - Branch: "master"<br/><br/>
31 * OpenEmbedded `meta-openembedded` Layer:
34 - Tested Revision: See the [`default.xml`](https://github.com/leon-anavi/AGL-repo/blob/master/default.xml)
35 manifest file for the `AGL-repo` repository for revision
38 Specifically, out of `meta-openembedded`, these sub-layers are used:
43 - `meta-python`<br/><br/>
45 * Yocto Project `meta-qt5` Layer from the
46 [OpenEmbedded Layer Index](https://layers.openembedded.org/layerindex/branch/master/layers/):
48 - URI: https://github.com/meta-qt5/meta-qt5.git
50 - Tested Revision: See the [`default.xml`](https://github.com/leon-anavi/AGL-repo/blob/master/default.xml)
51 manifest file for the `AGL-repo` repository for revision
52 information.<br/><br/>
54 ### Hardware Dependencies
56 Aside from the previously listed base dependencies, if you are using a
57 [supported Renesas board](../getting_started/reference/getting-started/machines/renesas.html)
58 supported Renesas board, these dependencies exist:
60 * AGL's `meta-renesas` Layer:
62 - URI: https://gerrit.automotivelinux.org/gerrit/AGL/meta-renesas
64 ### Feature Dependencies
66 The `meta-agl-demo` layer has the following AGL
67 [feature](../getting_started/reference/getting-started/image-workflow-initialize-build-environment.html#agl-features)
70 * Yocto Project `meta-security` Layer:
72 - URI: https://git.yoctoproject.org/cgit/cgit.cgi/meta-security
74 - Tested Revision: See the [`default.xml`](https://github.com/leon-anavi/AGL-repo/blob/master/default.xml)
75 manifest file for the `AGL-repo` repository for revision
76 information.<br/><br/>
78 * AGL's `meta-app-framework` Layer within the `meta-agl` Layer:
80 - URI: https://gerrit.automotivelinux.org/gerrit/gitweb?p=AGL/meta-agl.git
81 - Branch: "master"<br/><br/>
83 **The `agl-sota` Feature:**
85 * Here Technologies' `meta-updater` Layer:
87 - URI: https://github.com/advancedtelematic/meta-updater/
88 - Branch: "thud"<br/><br/>
90 * Here Technologies' `meta-updater-qemux86-64` Layer:
92 - URI: https://github.com/advancedtelematic/meta-updater-qemux86-64/
93 - Branch: "thud"<br/><br/>
95 * OpenEmbedded's `meta-openembedded` Layer:
97 - URI: https://github.com/openembedded/meta-openembedded
99 - Tested Revision: See the [`default.xml`](https://github.com/leon-anavi/AGL-repo/blob/master/default.xml)
100 manifest file for the `AGL-repo` repository for revision
103 Specifically, out of `meta-openembedded`, these sub-layers are used:
107 - `meta-python`<br/><br/>
109 **The `agl-netboot` Feature:**
111 * AGL's `meta-netboot` Layer within the `meta-agl` Layer:
113 - URI: https://gerrit.automotivelinux.org/gerrit/gitweb?p=AGL/meta-agl.git
120 [packagegroups](https://www.yoctoproject.org/docs/2.4.4/dev-manual/dev-manual.html#usingpoky-extend-customimage-customtasks)
121 consist of the following:
123 ### packagegroup-agl-demo-platform
125 This packagegroup is used for generating the `agl-demo-platform` image,
126 which is the full image for the AGL distributions IVI profile.
127 You can see the recipe (i.e. `agl-demo-platform.bb`) that installs
128 the `packagegroup-agl-demo-platform` packagegroup
129 [here](https://git.automotivelinux.org/AGL/meta-agl-demo/tree/recipes-platform/images/agl-demo-platform.bb).
131 As meta-agl's design of packagegroups, the `agl-demo-platform.bb` recipe installs
132 only `packagegroup-agl-demo-platform` and the packages of the DEMO applications.
134 ``agl-demo-platform`` contains the following three packagegroups:
136 * `packagegroup-agl-image-minimal`
137 * `packagegroup-agl-image-ivi`
138 * `packagegroup-agl-demo-platform`
140 ### packagegroup-agl-appfw*
142 These packagegroups contain packages for the AGL distribution's
143 Application Framework.
144 Subsystem should maintain `packagegroup-agl-appfw-[subsystem].bb`, which
145 should hold sufficient packages for the Application Framework.
147 Subsystems also can maintain their own packagegroups using appropriate
149 For example, Qt5 has two packagegroups in `meta-agl-demo`:
150 `packagegroup-agl-appfw-native-qt5` and `packagegroup-agl-demo-qt-examples`,
151 which are under `recipes-qt/`.
153 The `packagegroup-agl-appfw-native-qt5` is included by
154 `packagegroup-agl-appfw-native` because Qt5 belongs to native application
155 framework of AGL Distro.
157 Because the `packagegroup-agl-demo-qt-examples` is not mandatory for
158 the AGL Application Framework and the AGL DEMO, the packagegroup is added
159 to the layer's `local.conf` file only when needed.