No description
21e078a44a
createVariations relies on reusing the logicModule for the first variant in order to replace the original module in the global module map, which prevents leaving old split modules around in the global module map. Add comments to explain the behavior. Change-Id: Ia06d7fa4bc777e807241996d4e8bf977e641d741 |
||
|---|---|---|
| bootstrap | ||
| bpfmt | ||
| bpmodify | ||
| deptools | ||
| parser | ||
| pathtools | ||
| proptools | ||
| Blueprints | ||
| bootstrap.bash | ||
| build.ninja.in | ||
| context.go | ||
| context_test.go | ||
| doc.go | ||
| LICENSE | ||
| live_tracker.go | ||
| mangle.go | ||
| module_ctx.go | ||
| ninja_defs.go | ||
| ninja_strings.go | ||
| ninja_strings_test.go | ||
| ninja_writer.go | ||
| ninja_writer_test.go | ||
| package_ctx.go | ||
| README.md | ||
| scope.go | ||
| singleton_ctx.go | ||
| unpack.go | ||
| unpack_test.go | ||
Blueprint Build System
Blueprint is a meta-build system that reads in Blueprints files that describe modules that need to be built, and produces a Ninja (http://martine.github.io/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 langauge 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.