meta-agl-demo.md

   1 ## Introduction
   2
   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.
   8
   9 ## Layer Dependencies
  10
  11 This section describes dependencies for the `meta-agl-demo` layer.
  12 Dependencies are grouped into base, hardware, and feature dependencies.
  13
  14 ### Base Dependencies
  15
  16 The `meta-agl-demo` layer has the following base dependencies:
  17
  18 * Yocto Project Release:
  19
  20   - URI: git://git.yoctoproject.org/poky
  21   - Branch: "rocko"<br/><br/>
  22
  23 * AGL `meta-agl` Layer:
  24
  25   - URI: https://gerrit.automotivelinux.org/gerrit/AGL/meta-agl
  26   - Branch: "flounder"<br/><br/>
  27
  28 * OpenEmbedded `meta-openembedded` Layer:
  29
  30   - Branch: "rocko"
  31
  32     Specifically, out of `meta-openembedded`, these sub-layers are used:
  33
  34     - `meta-oe`
  35     - `meta-multimedia`
  36     - `meta-networking`
  37     - `meta-python`<br/><br/>
  38
  39 * Yocto Project `meta-qt5` Layer from the
  40   [OpenEmbedded Layer Index](https://layers.openembedded.org/layerindex/branch/master/layers/):
  41
  42   - URI: https://github.com/meta-qt5/meta-qt5.git
  43   - Branch:   "rocko"
  44
  45 ### Hardware Dependencies
  46
  47 Aside from the previously listed base dependencies, if you are using a
  48 [supported Renesas board](../getting_started/reference/getting-started/machines/renesas.html)
  49 supported Renesas board, these dependencies exist:
  50
  51 * AGL's `meta-renesas` Layer:
  52
  53   - URI: https://gerrit.automotivelinux.org/gerrit/AGL/meta-renesas
  54
  55 ### Feature Dependencies
  56
  57 The `meta-agl-demo` layer has the following AGL
  58 [feature](../getting_started/reference/getting-started/image-workflow-initialize-build-environment.html#agl-features)
  59 dependencies:
  60
  61 * Yocto Project `meta-security` Layer:
  62
  63   - URI: https://git.yoctoproject.org/cgit/cgit.cgi/meta-security
  64   - Branch: "rocko"<br/><br/>
  65
  66 * AGL's `meta-app-framework` Layer within the `meta-agl` Layer:
  67
  68   - URI: https://gerrit.automotivelinux.org/gerrit/gitweb?p=AGL/meta-agl.git
  69   - Branch: "flounder"
  70
  71 **The `agl-sota` Feature:**
  72
  73 * Here Technologies' `meta-updater` Layer:
  74
  75   - URI: https://github.com/advancedtelematic/meta-updater/
  76   - Branch: "rocko"<br/><br/>
  77
  78 * Here Technologies' `meta-updater-qemux86-64` Layer:
  79
  80   - URI: https://github.com/advancedtelematic/meta-updater-qemux86-64/
  81   - Branch: "rocko"<br/><br/>
  82
  83 * OpenEmbedded's `meta-openembedded` Layer:
  84
  85   - URI: https://github.com/openembedded/meta-openembedded
  86   - Branch: "rocko"
  87
  88     Specifically, out of `meta-openembedded`, these sub-layers are used:
  89
  90     - `meta-filesystems`
  91     - `meta-oe`<br/><br/>
  92
  93 **The `agl-netboot` Feature:**
  94
  95 * AGL's `meta-netboot` Layer within the `meta-agl` Layer:
  96
  97   - URI: https://gerrit.automotivelinux.org/gerrit/gitweb?p=AGL/meta-agl.git
  98   - Branch: "flounder"
  99
 100
 101 ## Packagegroups
 102
 103 AGL DEMO Platform's
 104 [packagegroups](https://www.yoctoproject.org/docs/2.4.4/dev-manual/dev-manual.html#usingpoky-extend-customimage-customtasks)
 105 consist of the following:
 106
 107 ### packagegroup-agl-demo-platform
 108
 109 This packagegroup is used for generating the `agl-demo-platform` image,
 110 which is the full image for the AGL distributions IVI profile.
 111 You can see the recipe (i.e. `agl-demo-platform.bb`) that installs
 112 the `packagegroup-agl-demo-platform` packagegroup
 113 [here](https://git.automotivelinux.org/AGL/meta-agl-demo/tree/recipes-platform/images/agl-demo-platform.bb).
 114
 115 As meta-agl's design of packagegroups, the `agl-demo-platform.bb` recipe installs
 116 only `packagegroup-agl-demo-platform` and the packages of the DEMO applications.
 117
 118 ``agl-demo-platform`` contains the following four packagegroups:
 119
 120   * `packagegroup-agl-image-minimal`
 121   * `packagegroup-agl-image-ivi`
 122   * `packagegroup-agl-demo-platform`
 123
 124 ### packagegroup-agl-appfw*
 125
 126 These packagegroups contain packages for the AGL distribution's
 127 Application Framework.
 128 Subsystem should maintain `packagegroup-agl-appfw-[subsystem].bb`, which
 129 should hold sufficient packages for the Application Framework.
 130
 131 Subsystems also can maintain their own packagegroups using appropriate
 132 `recipes-*/`.
 133 For example, Qt5 has two packagegroups in `meta-agl-demo`:
 134 `packagegroup-agl-appfw-native-qt5` and `packagegroup-agl-demo-qt-examples`,
 135 which are under `recipes-qt/`.
 136
 137 The `packagegroup-agl-appfw-native-qt5` is included by
 138 `packagegroup-agl-appfw-native` because Qt5 belongs to native application
 139 framework of AGL Distro.
 140
 141 Because the `packagegroup-agl-demo-qt-examples` is not mandatory for
 142 the AGL Application Framework and the AGL DEMO, the packagegroup is added
 143 to the layer's `local.conf` file only when needed.