7 The `meta-agl-demo` layer is the reference user interface layer for the DEMO
8 platform of Automotive Grade Linux (AGL).
9 The layer provides a reference platform and applications.
10 The BitBake target name for the DEMO platform is `agl-demo-platform`, which is
11 the full DEMO platform image.
15 This section describes dependencies for the `meta-agl-demo` layer.
16 Dependencies are grouped into base, hardware, and feature dependencies.
20 The `meta-agl-demo` layer has the following base dependencies:
22 - Yocto Project Release:
24 - URI: git://git.yoctoproject.org/poky
26 - Tested Revision: See the
27 [`default.xml`](https://github.com/leon-anavi/AGL-repo/blob/master/default.xml)
28 manifest file for the `AGL-repo` repository for revision information.
30 - AGL `meta-agl` Layer:
32 - URI: https://gerrit.automotivelinux.org/gerrit/AGL/meta-agl
35 - OpenEmbedded `meta-openembedded` Layer:
38 - Tested Revision: See the
39 [`default.xml`](https://github.com/leon-anavi/AGL-repo/blob/master/default.xml)
40 manifest file for the `AGL-repo` repository for revision information.
42 Specifically, out of `meta-openembedded`, these sub-layers are used:
49 - Yocto Project `meta-qt5` Layer from the
50 [OpenEmbedded Layer Index](https://layers.openembedded.org/layerindex/branch/master/layers/):
52 - URI: https://github.com/meta-qt5/meta-qt5.git
54 - Tested Revision: See the
55 [`default.xml`](https://github.com/leon-anavi/AGL-repo/blob/master/default.xml)
56 manifest file for the `AGL-repo` repository for revision information.
58 ### Hardware Dependencies
60 Aside from the previously listed base dependencies, if you are using a
61 [supported Renesas board](../../0_Getting_Started/2_Building_AGL_Image/5_3_RCar_Gen_3.md)
62 supported Renesas board, these dependencies exist:
64 - AGL's `meta-renesas` Layer:
66 - URI: https://gerrit.automotivelinux.org/gerrit/AGL/meta-renesas
68 ### Feature Dependencies
70 The `meta-agl-demo` layer has the following AGL [feature](../../0_Getting_Started/2_Building_AGL_Image/3_Initializing_Your_Build_Environment.md#agl-features)
73 - Yocto Project `meta-security` Layer:
75 - URI: https://git.yoctoproject.org/cgit/cgit.cgi/meta-security
77 - Tested Revision: See the
78 [`default.xml`](https://github.com/leon-anavi/AGL-repo/blob/master/default.xml)
79 manifest file for the `AGL-repo` repository for revision information.
81 - AGL's `meta-app-framework` Layer within the `meta-agl` Layer:
83 - URI: https://gerrit.automotivelinux.org/gerrit/gitweb?p=AGL/meta-agl.git
86 **The `agl-sota` Feature:**
88 - Here Technologies' `meta-updater` Layer:
90 - URI: https://github.com/advancedtelematic/meta-updater/
93 - Here Technologies' `meta-updater-qemux86-64` Layer:
95 - URI: https://github.com/advancedtelematic/meta-updater-qemux86-64/
98 - OpenEmbedded's `meta-openembedded` Layer:
100 - URI: https://github.com/openembedded/meta-openembedded
102 - Tested Revision: See the
103 [`default.xml`](https://github.com/leon-anavi/AGL-repo/blob/master/default.xml)
104 manifest file for the `AGL-repo` repository for revision information.
106 Specifically, out of `meta-openembedded`, these sub-layers are used:
112 **The `agl-netboot` Feature:**
114 - AGL's `meta-netboot` Layer within the `meta-agl` Layer:
116 - URI: https://gerrit.automotivelinux.org/gerrit/gitweb?p=AGL/meta-agl.git
122 AGL DEMO Platform's [packagegroups](https://www.yoctoproject.org/docs/3.1.2/dev-manual/dev-manual.html#usingpoky-extend-customimage-customtasks)
123 consist of the following:
125 - packagegroup-agl-demo-platform
127 This packagegroup is used for generating the `agl-demo-platform` image,
128 which is the full image for the AGL distributions IVI profile. You can see the
129 recipe (i.e. `agl-demo-platform.bb`) that installs the
130 `packagegroup-agl-demo-platform` packagegroup [here](https://git.automotivelinux.org/AGL/meta-agl-demo/tree/recipes-platform/images/agl-demo-platform.bb).
132 As meta-agl's design of packagegroups, the `agl-demo-platform.bb` recipe installs
133 only `packagegroup-agl-demo-platform` and the packages of the DEMO applications.
135 ``agl-demo-platform`` contains the following three packagegroups:
137 * `packagegroup-agl-image-minimal`
138 * `packagegroup-agl-image-ivi`
139 * `packagegroup-agl-demo-platform`
141 - packagegroup-agl-appfw*
143 These packagegroups contain packages for the AGL distribution's
144 Application Framework. Subsystem should maintain
145 `packagegroup-agl-appfw-[subsystem].bb`, which should hold sufficient packages
146 for the Application Framework.
148 Subsystems also can maintain their own packagegroups using appropriate
151 For example, Qt5 has two packagegroups in `meta-agl-demo`:
152 `packagegroup-agl-appfw-native-qt5` and `packagegroup-agl-demo-qt-examples`,
153 which are under `recipes-qt/`.
155 The `packagegroup-agl-appfw-native-qt5` is included by `packagegroup-agl-appfw-native` because Qt5 belongs to native application framework of AGL Distro.
157 Because the `packagegroup-agl-demo-qt-examples` is not mandatory for the AGL
158 Application Framework and the AGL DEMO, the packagegroup is added to the layer's
159 `local.conf` file only when needed.