5 https://git.automotivelinux.org/AGL/meta-agl-devel/plain/docs/../meta-agl-devel.md?h=master
8 <!-- WARNING: This file is generated by fetch_docs.js using /home/boron/Documents/AGL/docs-webtemplate/site/_data/tocs/devguides/master/meta-agl-devel-guides-devguides-book.yml -->
12 The `meta-agl-devel` layer contains components that are being tested or
14 The layer also contains software packages that Original Equipment
15 Manufacturers (OEMs) need but are not included in the AGL software.
19 The `meta-agl-devel` layer contains the following files and sub-layers:
23 ├── meta-agl-telemetry
24 ├── meta-audio-4a-framework
25 ├── meta-audio-soundmanager-framework
27 ├── meta-gstrecorder-rcar-gen3
28 ├── meta-hmi-framework
29 ├── meta-oem-extra-libs
34 The following list provides a summary of these sub-layers:
36 * `meta-agl-telemetry`: Provides the smallest AGL image.
37 The image is designed to be used when a device requires restricted
38 scope of responsibilites (e.g. collecting vehicle telemetry).
40 * `meta-audio-4a-framework`: A collection of recipes used for the
41 first integration of 4A (i.e. Advanced AGL Audio Architecture).
43 * `meta-pipewire`: A collection of recipes used for the integration
44 of the pipewire sound system.
46 * `meta-audio-soundmanager-framework`: Supports the Soundmanager
47 Audio Framework features, which maps to the `agl-audio-soundmanager-framework`
50 * `meta-egvirt`: The AGL Virtualization Expert Group (EG-VIRT) layer.
51 This layer supports the design, test, implementation, and assessment
52 of virtualization technologies (e.g. containers, hypervisors, system
53 partitioners, and so forth) aimed at AGL ARMv8 and Intel platforms.
55 * `meta-gstrecorder-rcar-gen3`: Supports streaming audio and video for
56 the Pro and Premier board kits (e.g.
57 [Renesas R-Car Starter Kit Pro Board](https://www.elinux.org/R-Car/Boards/M3SK)
59 [Renesas R-Car Starter Kit Premier Board](https://www.elinux.org/R-Car/Boards/H3SK)).
61 * `meta-hmi-framework`: Provides AGL's Human Machine Interface (HMI) framework
62 through resource management consisting of sounds, windows, and input control.
63 For more information, see the
64 [HMI-Framework Page](https://wiki.automotivelinux.org/hmiframework) of the
67 * `meta-oem-extra-libs`: Provides libraries and software packages needed by
68 OEMs but not provided by the AGL software.
70 * `templates`: Feature templates that support the `meta-agl-devel` layer.
72 ## Additional Sub-Layer Information
74 This section provides additional information for the `meta-egvirt`,
75 `meta-oem-extra-libs`, and `meta-hmi-framework` layers.
77 ### Virtualization Support
79 The `meta-egvirt` layer enables virtualization support in AGL.
80 The AGL Virtualization Expert (EG-VIRT) group is responsible
81 for design and implementation of AGL virtualization solutions
82 (.e.g the Virtualization platform architecture of AGL).
83 You can read about EG-VERT's efforts on the
84 "[Virtualization Expert Group's](https://wiki.automotivelinux.org/eg-virt)"
87 Additionally, you can learn more about virtualization as it applies to AGL
89 "[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)"
92 ### OEM Extra Libraries
94 The `meta-oem-extra-libs` layer provides additional software packages many OEMs need
95 but are not part of the AGL source.
96 Following is the list of packages this layer provides:
118 To add these packages to your library, you need to include the
119 `agl-oem-extra-libs` AGL feature when you initialize your build
120 environment using the `aglsetup.sh` script.
122 For information on how to use the `aglsetup.sh` script to initialize
123 your build environment, see the
124 "[Initializing Your Build Environment](../getting_started/reference/getting-started/image-workflow-initialize-build-environment.html)"
127 Once you have included the AGL feature, you can build your image.
131 The `meta-hmi-framework` layer supports the Human-Machine Interface (HMI) Framework.
132 The HMI-Framework is the User Interface (UI) to control the Infotainment System.
133 Work continues to close the gap between the user experience of a smart phone
134 and the Infotainment System in a vehicle, for example.
136 You can find more out about HMI Framework progress on the
137 "[HMI Framework](https://wiki.automotivelinux.org/hmiframework)" page on the AGL Wiki.
139 To add HMI Framework support to your image, you need to include the
140 `hmi-framework` AGL feature when you initialize your build
141 environment using the `aglsetup.sh` script.
143 For information on how to use the `aglsetup.sh` script to initialize
144 your build environment, see the
145 "[Initializing Your Build Environment](../getting_started/reference/getting-started/image-workflow-initialize-build-environment.html)"
148 Once you have included the AGL feature, you can build your image.