Overview

Linaro uses a common manifest file for (almost) all of the android devices we support, default.xml. In order to not force users who are only interested in one device to download projects specific to some other device we use several repo groups.

Previously Linaro used different manifest files for different android devices.

Working with the common manifest

Init and sync for all devices:

$repo init -u <manifest git> -b <branch>

for instance:

$repo init -u git://android.git.linaro.org/platform/manifest.git -b linaro_android_4.2.2

Init and sync for a specific device

$repo init -u <manifest git> -b <branch> -g <groups>

for instance:

$repo init -u git://android.git.linaro.org/platform/manifest.git -b linaro_android_4.2.2 -g "common,vexpress,devel"

Note that there no longer is any need to specify the manifest file to use via -m

Working with groups

As seen above the -g flag can be used in repo init to specify which groups to fetch. When using this only projects matching the specified groups will be fetched during sync.

In order to handle this a special group, common, has been added. All projects that are valid for all supported devices are part of this group. When fetching a forest for a specific device the set of groups to use would be: common + <device group> + <optional extras>

Currently the following groups have been added to the manifest:

  • arndale, support for arndale
  • common, all projects which are relevant for all devices
  • devel, support for compilation on target
  • galaxynexus, support for galaxynexus
  • nexus7, support for nexus7
  • pandaboard, support for panda
  • snowball, support for snowball
  • vexpress, support for vexpress
  • vexpress-iks, support for vexpress-iks
  • vexpress-tests, a set of tests, typically run on vexpress with linux-linaro

Devices not supported by the common manifest

  • origen quad, use tracking-origen-quad.xml

Platform/Android/WorkWithCommonManifest (last modified 2013-03-27 12:40:08)