Make apenwarr/redo installable on windows and work with uv tool install
After waiting for children to exit, we would release our own token, and then the caller would immediately try to obtain a token again. This accounted for tokens correctly, but would pass tokens around the call tree in unexpected ways. For example, imagine we had only one token. We call 'redo a1 a2', and a1 calls 'redo b1 b2', and b1 calls 'redo c1'. When c1 exits, it releases its token, then tries to re-acquire it before exiting. This also includes 'redo b1 b2' and 'redo a1 a2' in the race for the token, which means b1 might get suspended while *either* a2 or b2 starts running. This never caused a deadlock, even if a2 or b2 depends on b1, because if they tried to build b1, they would notice it is locked, give up their token, and wait for the lock. c1 (and then b1) could then obtain the token and immediately terminate, allowing progress to continue. But this is not really the way we expect things to happen. "Obviously" what we want here is a straightforward stack unwinding: c1 should finish, then b1, then b2, then a1, then b2. The not-very-obvious symptom of this bug is that redo's unit tests seemed to run in the wrong order when using -j1 --no-log. (--log would hide the problem by rearranging logs back into the right order!) |
||
|---|---|---|
| bin | ||
| contrib/bash_completion.d | ||
| docs | ||
| minimal | ||
| redo | ||
| t | ||
| .gitignore | ||
| .pylintrc | ||
| all.do | ||
| clean.do | ||
| do | ||
| install.do | ||
| LICENSE | ||
| Makefile | ||
| mkdocs.yml | ||
| README.md | ||
| test.do | ||
redo - a recursive build system
Smaller, easier, more powerful, and more reliable than make.
This is an implementation of Daniel J. Bernstein's redo build system. He never released his version, so other people have implemented different variants based on his published specification.
This version, sometimes called apenwarr/redo, is probably the most advanced one, including parallel builds, improved logging, extensive automated tests, and helpful debugging features.
To build and test redo, run ./do -j10 test. To install it, run
DESTDIR=/tmp/testinstall PREFIX=/usr/local ./do -j10 install.
- View the documentation via readthedocs.org
- Visit the source code on github
- Discussions and support via the
mailing list (archives).
You can subscribe by sending any email message to
redo-list+subscribe@googlegroups.com(note the plus sign).