aosp-part-getting-started

Navigate AOSP source tree, repo sync, lunch targets, and Soong/Bazel build systems.

122|30|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/aospbooks/aosp-internal-book --skill aosp-part-getting-started
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aosp-part-getting-started
Source: https://github.com/aospbooks/aosp-internal-book/tree/main/agents/claude/skills/aosp-part-getting-started
Command: npx skills add https://github.com/aospbooks/aosp-internal-book --skill aosp-part-getting-started

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AOSP Part I provides foundational orientation to the Android Open Source Project, outlining how to reason about the source tree, the repo/manifest workflow, the Soong (Android.bp) and Bazel/Kleaf build systems, lunch targets, the m build entry point, and aconfig feature flags across build-time vs runtime ramp/cleanup workflows. Chapters 0–3 (Frontmatter, Introduction, Source Code & Build System, Feature Flags) are designed to give readers a practical map of where everything lives and how to begin hands-on exploration.

Core Features & Use Cases

  • Orientation to the AOSP repository structure, key chapters, and how the pieces fit together for platform engineering, ROM development, and system integration.
  • Guidance on syncing with repo, using lunch targets, the m workflow, and understanding Android.bp (Soong) and Bazel-based approaches to building images.
  • Clear path for ramp-up and cleanup workflows, enabling incremental contributions and safe navigation through the tree.

Quick Start

Clone the AOSP repository with repo, run repo sync to fetch the tree, and start with Chapters 0–3 to gain orientation.

Frequently Asked Questions about aosp-part-getting-started

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync and build the AOSP source tree using repo and m?

To sync and build AOSP, clone with repo, run repo sync to fetch the multi-repo source tree, select a lunch target, and execute the m build entry point to generate system images.

What is the difference between Soong Android.bp and Bazel Kleaf build systems in AOSP?

Soong uses Android.bp files for build configuration, while Bazel Kleaf offers an alternative build approach. AOSP supports mixed builds, allowing both to coexist for generating platform images.

How do aconfig feature flags work for build-time and runtime workflows in AOSP?

Aconfig feature flags manage build-time and runtime toggles across ramp and cleanup workflows in AOSP. They enable incremental contributions and safe navigation through the source tree.

Do I need repo and lunch targets to start AOSP platform development?

Yes, repo is required to fetch the multi-repo source tree, and lunch targets configure the build environment before invoking the m entry point for Android image generation.

What is the best way to navigate the AOSP multi-repo manifest workflow?

The best way to navigate the AOSP manifest workflow is using the repo tool to sync the multi-repo source tree, providing a practical map of where everything lives for platform engineering.