Streamline Platform Approaches for Android
Builds
● Agenda
○ Meta-info of the builds for LAVA and l-a-m-c
○ Documentation ...
Meta-info of the builds for LAVA and linaro
image tools
● Current Setup
○ Bootargs are currently set by l-a-m-c.
○ Can't u...
Meta-info of the builds for LAVA and linaro
image tools
● Use of Meta-info to pass info about
○ Bootargs from the build.
○...
Documentation Process
● Documentation on a.b.l.o,snapshots.l.o,releases.linaro.
org through predifined texts .
○ Release N...
Current Build Process
● Fetch toolchain externally instead of using repo.
● 17 Manifests in linaro_android_4.1.2 branch.
●...
How far can and should we move from AOSP
● We have added packages like busybox ffmpeg which
use different kinds of Makefil...
CI loop for kernel in Android
● Need to setup CI loop for kernels.
● Need to add hooks to enable or disable userspace
feat...
Fastboot support in LAVA
Can fastboot protocol be an alternative to master image for
testing AOSP supported devices ?
Toolchain Integration in the build
● Available Options
○ Integrate compilation of toolchain as part of source?
○ Check in ...
Thank you
Upcoming SlideShare
Loading in …5
×

LCE12: Streamline Platform Approaches for Android Builds

128
-1

Published on

Resource: LCE12
Name: Streamline Platform Approaches for Android Builds
Date: 29-10-2012
Speaker: Vishal Bhoj

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
128
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

LCE12: Streamline Platform Approaches for Android Builds

  1. 1. Streamline Platform Approaches for Android Builds ● Agenda ○ Meta-info of the builds for LAVA and l-a-m-c ○ Documentation process. ○ Current build process. ○ How far can and should we deviate from AOSP. ○ CI loop for kernel in Android. ○ Fastboot support in LAVA. ○ Toolchain Integration in the build.
  2. 2. Meta-info of the builds for LAVA and linaro image tools ● Current Setup ○ Bootargs are currently set by l-a-m-c. ○ Can't use the same setup at LAVA for FM across all builds. ○ Installation of binaries are currently exported as build variables for LAVA. ○ A new user cannot decide when the graphics installer script needs to be used.
  3. 3. Meta-info of the builds for LAVA and linaro image tools ● Use of Meta-info to pass info about ○ Bootargs from the build. ○ Right dtb to be used by l-a-m-c. ○ Pop Instructions or run installer for end user. ● Something similar to hardware packs ■ https://wiki.linaro.org/HardwarePacksV3
  4. 4. Documentation Process ● Documentation on a.b.l.o,snapshots.l.o,releases.linaro. org through predifined texts . ○ Release Notes ○ Binary Image Installation ○ Building From Source ○ Firmware Update https://blueprints.launchpad.net/linaro-license-protection/+spec/support- predefined-text-files
  5. 5. Current Build Process ● Fetch toolchain externally instead of using repo. ● 17 Manifests in linaro_android_4.1.2 branch. ● Not compatible to AOSP build procedure.
  6. 6. How far can and should we move from AOSP ● We have added packages like busybox ffmpeg which use different kinds of Makefiles ○ These libraries can't be linked with other libraries which include conventional android build methods. ● We have kernel,u-boot built as part of AOSP
  7. 7. CI loop for kernel in Android ● Need to setup CI loop for kernels. ● Need to add hooks to enable or disable userspace features like support for hardware accelerated graphics depending on the support available in the kernel.
  8. 8. Fastboot support in LAVA Can fastboot protocol be an alternative to master image for testing AOSP supported devices ?
  9. 9. Toolchain Integration in the build ● Available Options ○ Integrate compilation of toolchain as part of source? ○ Check in prebuilt toolchain into git. ○ Any other suggestions ?
  10. 10. Thank you
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×