diff options
author | Evan Martin <martine@danga.com> | 2010-12-13 16:30:38 (GMT) |
---|---|---|
committer | Evan Martin <martine@danga.com> | 2010-12-13 16:30:38 (GMT) |
commit | 76327856c43414940c210325858b35b5fea09360 (patch) | |
tree | 13d59bcf081e3c7d4aeb342525d4875cd1596b29 /todo | |
parent | e96bcd77942fe26f6c3c2ff8e1541f66dec3a230 (diff) | |
download | Ninja-76327856c43414940c210325858b35b5fea09360.zip Ninja-76327856c43414940c210325858b35b5fea09360.tar.gz Ninja-76327856c43414940c210325858b35b5fea09360.tar.bz2 |
todo updates
Diffstat (limited to 'todo')
-rw-r--r-- | todo | 21 |
1 files changed, 6 insertions, 15 deletions
@@ -1,19 +1,10 @@ save command lines + or use mtimes on build files? "explain" mode that shows why we're building a file "one file" mode that builds only outputs of a single file +"dry run" mode that shows command lines but doesn't build +adjust to system load dynamically -short-term ideas: -- magic $in/$out variables shouldn't be magic, they're just a shortcut - for specifying commands like - rule frob - command = frob $manual_inputs - build foo: frob - manual_inputs = a b c - -longer-term ideas: - -- use lemon/ragel for parsing - -- progress bar rather than printing commands in series - -- store historical timing info, allowing etas on builds +progress bar rather than printing commands in series +store historical timing info, allowing etas on builds + how does parallelization fit in? |