Make apenwarr/redo installable on windows and work with uv tool install
Because redo targets are nicely isolated (unlike make targets), you usually only want to debug one of them at a time. Using -x could be confusing, because you might end up with a dump of output from a dependency you're not interested in. Now, by default we'll disable -x when recursing into sub-targets, so you only see the trace from the targets you are actually trying to debug. To get recursive behaviour, specify -x twice, eg. -xx. Same idea with -v. |
||
|---|---|---|
| bin | ||
| contrib/bash_completion.d | ||
| docs | ||
| minimal | ||
| redo | ||
| redoconf | ||
| t | ||
| .gitignore | ||
| .pylintrc | ||
| all.do | ||
| clean.do | ||
| do | ||
| install.do | ||
| LICENSE | ||
| Makefile | ||
| MANIFEST.in | ||
| mkdocs.yml | ||
| README.md | ||
| setup.py | ||
| 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).