| commit | 987ed9ba299b441c5c0306b1fa07f720204c11ef | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Wed Oct 18 14:15:24 2017 -0700 |
| committer | Dan Willemsen <dwillemsen@google.com> | Wed Oct 18 15:11:03 2017 -0700 |
| tree | 20b7088ef07f96e9d5cba219f517c9147f9d5621 | |
| parent | 5fa3f89f2cc180d223aee468e3a1298604f01d25 [diff] |
Add file locking to microfactory To prevent against multiple instances attempting to rebuild the same executable, add a file lock to Build(). The trace file may not be consistent in this case, but everything that reads it should be able to handle a corrupted trace file. Test: `while true; do <microfactory-enabled executable>; done` in parallel, and modify the code to microfactory (echo "//" >>microfactory.go) Change-Id: I30cb22bb9c790c57c507354127d4a5f82526a489
1 file changed
tree: 20b7088ef07f96e9d5cba219f517c9147f9d5621
- 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
- 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.