| commit | 75fec88fc62a330cc2bc4ef40011b5401e8dc40f | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Thu Jun 22 17:01:24 2017 -0700 |
| committer | Dan Willemsen <dwillemsen@google.com> | Thu Jun 22 17:53:39 2017 -0700 |
| tree | aaf1513b3caddccbf81d2644721d942a44518e41 | |
| parent | 28c7837b3dc409a2ce601db411eb6578cbec4933 [diff] |
Fix glob deps for non-wild patterns Patterns that were not wild would return an empty "dirs" list if the file was found. But then if they were removed, we wouldn't know to update the glob file and re-run the primary builder. In this case, instead of adding the final directory into the dirs list, add the matched files themselves. Due to editors performing atomic writes (the directory timestamp often gets updated at the same time as file timestamp) this is probably more efficient. In either case, we're only re-running the individual glob, which is rather cheap. Rename startGlob/Glob return name from "dirs" to "deps" since it may contain files now too.
2 files changed
tree: aaf1513b3caddccbf81d2644721d942a44518e41
- bootstrap/
- bpfmt/
- bpmodify/
- deptools/
- gotestmain/
- gotestrunner/
- loadplugins/
- parser/
- pathtools/
- proptools/
- tests/
- .gitignore
- .travis.fix-fork.sh
- .travis.gofmt.sh
- .travis.install-ninja.sh
- .travis.yml
- blueprint.bash
- Blueprints
- bootstrap.bash
- build.ninja.in
- context.go
- context_test.go
- CONTRIBUTING.md
- doc.go
- glob.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
- 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.