diff options
| author | Evan Martin <martine@danga.com> | 2012-05-07 15:53:26 (GMT) |
|---|---|---|
| committer | Evan Martin <martine@danga.com> | 2012-05-08 16:07:04 (GMT) |
| commit | d73af72473a926bf7a90dcf35d902158dc8106c9 (patch) | |
| tree | 05cbef833951c92b3aba84e3f4c56cb70c70988a | |
| parent | 23788bd7faddc85f7ec2dd6f7446d048a8b61dd2 (diff) | |
| download | Ninja-d73af72473a926bf7a90dcf35d902158dc8106c9.zip Ninja-d73af72473a926bf7a90dcf35d902158dc8106c9.tar.gz Ninja-d73af72473a926bf7a90dcf35d902158dc8106c9.tar.bz2 | |
clarify what i mean by "policy"
| -rw-r--r-- | doc/manual.asciidoc | 10 |
1 files changed, 8 insertions, 2 deletions
diff --git a/doc/manual.asciidoc b/doc/manual.asciidoc index f34b800..d9a6188 100644 --- a/doc/manual.asciidoc +++ b/doc/manual.asciidoc @@ -50,8 +50,14 @@ Here are the design goals of Ninja: * very fast (i.e., instant) incremental builds, even for very large projects. -* very little policy about how code is built; "explicit is better than - implicit". +* very little policy about how code is built. Different projects and + higher-level build systems have different opinions about how code + should be built; for example, should built objects live alongside + the sources or should all build output go into a separate directory? + Is there an "package" rule that builds a distributable package of + the project? Sidestep these decisions by trying to allow either to + be implemented, rather than choosing, even if that results in + more verbosity. * get dependencies correct, and in particular situations that are difficult to get right with Makefiles (e.g. outputs need an implicit |