Google Git
Sign in
android / platform / build / blueprint / refs/tags/android-n-preview-4
tag78d3db51d6073786cecd5d2cc6a4c4b07afe4627
taggerThe Android Open Source Project <initial-contribution@android.com>Mon Jun 27 10:36:55 2016 -0700
objectac5ace67024f19917febc95468fd9d37088c1fd8 
Android N Preview 4 (NPD56N)
commitac5ace67024f19917febc95468fd9d37088c1fd8[log] [tgz]
authorColin Cross <ccross@android.com>Thu Jun 09 11:04:12 2016 -0700
committerColin Cross <ccross@android.com>Thu Jun 09 18:22:58 2016 +0000
tree16b68a65b75fa320a3fb539d92705c94b22a34dc
parent0c42d4b31de3ee36c483c830b137829d134b02ce [diff]
parentd4f49b07d1b4b80da2e1234b2e9a37eb6a50ba55 [diff]
Merge remote-tracking branch 'aosp/upstream' into master

3a17686 Merge remote-tracking branch 'aosp/upstream' into master
d4f49b0 Merge pull request #103 from colincross/parser
e32cc80 Refactor blueprint parser nodes to an interface
aedd490 Merge pull request #101 from colincross/doc
7932496 Fix documentation property type for pointers
d9f6fd5 Remove naming stutter in bpdoc
017ed2e Fix govet issues

Change-Id: Ie0863b79ee0d22ae6dbc066ca06303f046d904b7
tree: 16b68a65b75fa320a3fb539d92705c94b22a34dc
  1. bootstrap/
  2. bpfmt/
  3. bpmodify/
  4. choosestage/
  5. deptools/
  6. gotestmain/
  7. gotestrunner/
  8. loadplugins/
  9. parser/
  10. pathtools/
  11. proptools/
  12. tests/
  13. .gitignore
  14. .travis.fix-fork.sh
  15. .travis.install-ninja.sh
  16. .travis.yml
  17. blueprint.bash
  18. Blueprints
  19. bootstrap.bash
  20. build.ninja.in
  21. context.go
  22. context_test.go
  23. context_test_Blueprints
  24. CONTRIBUTING.md
  25. doc.go
  26. LICENSE
  27. live_tracker.go
  28. mangle.go
  29. module_ctx.go
  30. ninja_defs.go
  31. ninja_strings.go
  32. ninja_strings_test.go
  33. ninja_writer.go
  34. ninja_writer_test.go
  35. package_ctx.go
  36. README.md
  37. scope.go
  38. singleton_ctx.go
  39. splice_modules_test.go
  40. unpack.go
  41. unpack_test.go
README.md

Blueprint Build System

Build Status

Blueprint is a meta-build system that reads in Blueprints files that describe modules that need to be built, and produces a Ninja manifest describing the commands that need to be run and their dependencies. Where most build systems use built-in rules or a domain-specific language to describe the logic for converting module descriptions to build rules, Blueprint delegates this to per-project build logic written in Go. For large, heterogenous projects this allows the inherent complexity of the build logic to be maintained in a high-level language, while still allowing simple changes to individual modules by modifying easy to understand Blueprints files.