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
137
138
139
140
141
142
143
|
## Introduction
The `meta-agl-devel` layer contains components that are being tested or
still in development.
The layer also contains software packages that Original Equipment
Manufacturers (OEMs) need but are not included in the AGL software.
## Sub-Layers
The `meta-agl-devel` layer contains the following files and sub-layers:
```
.
├── meta-agl-telemetry
├── meta-audio-4a-framework
├── meta-audio-soundmanager-framework
├── meta-egvirt
├── meta-gstrecorder-rcar-gen3
├── meta-hmi-framework
├── meta-oem-extra-libs
├── README.md
├── templates
```
The following list provides a summary of these sub-layers:
* `meta-agl-telemetry`: Provides the smallest AGL image.
The image is designed to be used when a device requires restricted
scope of responsibilites (e.g. collecting vehicle telemetry).
* `meta-audio-4a-framework`: A collection of recipes used for the
first integration of 4A (i.e. Advanced AGL Audio Architecture).
<!--section-note-->
**NOTE:**
Recipes from this layer will be integrated into the
`meta-agl` layer in the future.
<!--end-section-note-->
* `meta-audio-soundmanager-framework`: Supports the Soundmanager
Audio Framework features, which maps to the `agl-audio-soundmanager-framework`
AGL feature.
* `meta-egvirt`: The AGL Virtualization Expert Group (EG-VIRT) layer.
This layer supports the design, test, implementation, and assessment
of virtualization technologies (e.g. containers, hypervisors, system
partitioners, and so forth) aimed at AGL ARMv8 and Intel platforms.
* `meta-gstrecorder-rcar-gen3`: Supports streaming audio and video for
the Pro and Premier board kits (e.g.
[Renesas R-Car Starter Kit Pro Board](https://www.elinux.org/R-Car/Boards/M3SK)
and
[Renesas R-Car Starter Kit Premier Board](https://www.elinux.org/R-Car/Boards/H3SK)).
* `meta-hmi-framework`: Provides AGL's Human Machine Interface (HMI) framework
through resource management consisting of sounds, windows, and input control.
For more information, see the
[HMI-Framework Page](https://wiki.automotivelinux.org/hmiframework) of the
AGL Wiki.
* `meta-oem-extra-libs`: Provides libraries and software packages needed by
OEMs but not provided by the AGL software.
* `templates`: Feature templates that support the `meta-agl-devel` layer.
## Additional Sub-Layer Information
This section provides additional information for the `meta-egvirt`,
`meta-oem-extra-libs`, and `meta-hmi-framework` layers.
### Virtualization Support
The `meta-egvirt` layer enables virtualization support in AGL.
The AGL Virtualization Expert (EG-VIRT) group is responsible
for design and implementation of AGL virtualization solutions
(.e.g the Virtualization platform architecture of AGL).
You can read about EG-VERT's efforts on the
"[Virtualization Expert Group's](https://wiki.automotivelinux.org/eg-virt)"
page of the AGL wiki.
Additionally, you can learn more about virtualization as it applies to AGL
by reading
"[The Automotive Grade Linux Software Defined Connected Car Architecture](https://www.automotivelinux.org/wp-content/uploads/sites/4/2018/06/agl_software_defined_car_jun18.pdf)"
whitepaper.
### OEM Extra Libraries
The `meta-oem-extra-libs` layer provides additional software packages many OEMs need
but are not part of the AGL source.
Following is the list of packages this layer provides:
* boost
* fixesproto
* imagemagick
* iptables
* Xorg-macros
* zlib
* eglibc = glibc
* libcurl
* libgif
* libneon
* mongoose
* fuse
* protocol buffers
* bsdiff
* module-init-tools
* libcroco
* libtiff
* librsvg
* libpcap
To add these packages to your library, you need to include the
`agl-oem-extra-libs` AGL feature when you initialize your build
environment using the `aglsetup.sh` script.
For information on how to use the `aglsetup.sh` script to initialize
your build environment, see the
"[Initializing Your Build Environment](../getting_started/reference/getting-started/image-workflow-initialize-build-environment.html)"
section.
Once you have included the AGL feature, you can build your image.
### HMI Framework
The `meta-hmi-framework` layer supports the Human-Machine Interface (HMI) Framework.
The HMI-Framework is the User Interface (UI) to control the Infotainment System.
Work continues to close the gap between the user experience of a smart phone
and the Infotainment System in a vehicle, for example.
You can find more out about HMI Framework progress on the
"[HMI Framework](https://wiki.automotivelinux.org/hmiframework)" page on the AGL Wiki.
To add HMI Framework support to your image, you need to include the
`hmi-framework` AGL feature when you initialize your build
environment using the `aglsetup.sh` script.
For information on how to use the `aglsetup.sh` script to initialize
your build environment, see the
"[Initializing Your Build Environment](../getting_started/reference/getting-started/image-workflow-initialize-build-environment.html)"
section.
Once you have included the AGL feature, you can build your image.
|
