No description
77418b70b4
Parser.parseVariable method should always set the value of the variable it creates. Failure to do so may end up in the following: ``` $ androidmk <(printf "FOO:=(X)\nFOO:=bar\n") parse error: <input>:3:1: variable already set, previous assignment: FOO@<input>:1:5 = %!s(PANIC=String method: runtime error: invalid memory address or nil pointer dereference) (%!s(PANIC=String method: runtime error: invalid memory address or nil pointer dereference)) false ``` The cause is that calling Parser.Parse to parse `FOO=abc` created a Variable instance with nil value, causing panic on print attempt. Test: m androidmk && androidmk <(printf "FOO:=(X)\nFOO:=bar\n") (should print: ERROR: parse error: <input>:3:1: variable already set, previous assignment: FOO@<input>:1:5 = X = Not Evaluated (X = Not Evaluated) false) Change-Id: I296d7984df6d8796e0075f9eb692b234f8c94f08 |
||
|---|---|---|
| bootstrap | ||
| bpfmt | ||
| bpmodify | ||
| deptools | ||
| gotestmain | ||
| gotestrunner | ||
| loadplugins | ||
| microfactory | ||
| parser | ||
| pathtools | ||
| proptools | ||
| tests | ||
| .gitignore | ||
| .travis.fix-fork.sh | ||
| .travis.gofmt.sh | ||
| .travis.install-ninja.sh | ||
| .travis.yml | ||
| blueprint.bash | ||
| blueprint_impl.bash | ||
| Blueprints | ||
| bootstrap.bash | ||
| context.go | ||
| context_test.go | ||
| CONTRIBUTING.md | ||
| doc.go | ||
| glob.go | ||
| glob_test.go | ||
| go.mod | ||
| LICENSE | ||
| live_tracker.go | ||
| mangle.go | ||
| module_ctx.go | ||
| module_ctx_test.go | ||
| name_interface.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 | ||
| splice_modules_test.go | ||
| visit_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 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.