| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
The resulting redo binary behaves differently if called with each
respective redo-* name, and is symlinked to the different command names.
This should reduce the memory footprint of a redo build, as the OS only
needs to keep one copy of the redo code in memory.
|
| |
|
|
|
|
|
|
| |
It's done a lot more efficiently now, as we are no longer checking if a
target is out-of-date before we rebuild it, but instead rebuild
subtargets directly when they are checked.
We also now correctly depend on .do files.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
This includes two different scenarios, first if the do-files which was
used to build the target has changed the target must be rebuilt.
Second, if a target was build by a lower priority do-file, like
default.fuu.do, then it must be rebuilt if <target>.fuu.do appears.
Note that at this point, Redofile as do-file is semi-supported, as it's
future is uncertain.
|
| |
|
