| commit | fdeaf881f44fbccf478112bda2d091b20b65cc0f | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Wed Mar 21 17:00:39 2018 -0700 |
| committer | Colin Cross <ccross@android.com> | Tue Apr 10 16:43:51 2018 -0700 |
| tree | ab7f77fd5be24bd44705dc613a01be224fefd267 | |
| parent | ff2c5b4cc808246366338b6d31aa5616e08f113d [diff] |
Make End() return the position after the node End() was previously only used to determine if a comment was within a Node, so it used the expedient definition of the position of the last token in the node. In the next patch it will be used for capturing substrings of the Blueprint file, so make it point to the character after the last token instead. Also add tests for it. Test: parser_test.go Change-Id: Icaff3915b41e251ef9d0aad5615021bf37406aee
3 files changed
tree: ab7f77fd5be24bd44705dc613a01be224fefd267
- 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
- LICENSE
- live_tracker.go
- mangle.go
- module_ctx.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
- unpack.go
- unpack_test.go
- visit_test.go
README.md
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.