1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
|
## Introduction
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.
## Layer Dependencies
This section describes dependencies for the `meta-agl-demo` layer.
Dependencies are grouped into base, hardware, and feature dependencies.
### Base Dependencies
The `meta-agl-demo` layer has the following base dependencies:
* Yocto Project Release:
- URI: git://git.yoctoproject.org/poky
- Branch: "rocko"<br/><br/>
* AGL `meta-agl` Layer:
- URI: https://gerrit.automotivelinux.org/gerrit/AGL/meta-agl
- Branch: "guppy"<br/><br/>
* OpenEmbedded `meta-openembedded` Layer:
- Branch: "rocko"
Specifically, out of `meta-openembedded`, these sub-layers are used:
- `meta-oe`
- `meta-multimedia`
- `meta-networking`
- `meta-python`<br/><br/>
* 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: "rocko"
### Hardware Dependencies
Aside from the previously listed base dependencies, if you are using a
[supported Renesas board](../../../../getting_started/en/dev/reference/machines/renesas.html)
supported Renesas board, these dependencies exist:
* AGL's `meta-renesas` Layer:
- URI: https://gerrit.automotivelinux.org/gerrit/AGL/meta-renesas
### Feature Dependencies
The `meta-agl-demo` layer has the following AGL
[feature](../getting_started/reference/getting-started/image-workflow-initialize-build-environment.html#agl-features)
dependencies:
* Yocto Project `meta-security` Layer:
- URI: https://git.yoctoproject.org/cgit/cgit.cgi/meta-security
- Branch: "rocko"<br/><br/>
* AGL's `meta-app-framework` Layer Within the `meta-agl` Layer:
- URI: https://gerrit.automotivelinux.org/gerrit/gitweb?p=AGL/meta-agl.git
- Branch: "guppy"
**The `agl-sota` Feature:**
* AGL's `meta-sota` Layer Within the `meta-agl-extra` Layer:
- URI: https://gerrit.automotivelinux.org/gerrit/gitweb?p=AGL/meta-agl-extra.git
- Branch: "guppy"<br/><br/>
* OpenEmbedded's `meta-openembedded` Layer:
- URI: https://github.com/openembedded/meta-openembedded
- Branch: "rocko"
In particular, the `meta-openembedded` layer depends on the
`meta-filesystems` sub-layer.
**The `agl-netboot` Feature:**
* AGL's `meta-netboot` Layer Within the `meta-agl` Layer:
- URI: https://gerrit.automotivelinux.org/gerrit/gitweb?p=AGL/meta-agl.git
- Branch: "guppy"
## 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
only `packagegroup-agl-demo-platform` and the packages of the DEMO applications.
``agl-demo-platform`` contains the following four packagegroups:
* `packagegroup-agl-image-minimal`
* `packagegroup-agl-image-ivi`
* `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/`.
The `packagegroup-agl-appfw-native-qt5` is included by
`packagegroup-agl-appfw-native` because Qt5 belongs to native application
framework of AGL Distro.
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.
|
