Make apenwarr/redo installable on windows and work with uv tool install
9b6d1eeb6e
Merge the two files into env, and make each command explicitly call the function that sets it up in the way that's needed for that command. This means we can finally just import all the modules at the top of each file, without worrying about import order. Phew. While we're here, remove the weird auto-appending-'all'-to-targets feature in env.init(). Instead, do it explicitly, and only from redo and redo-ifchange, only if is_toplevel and no other targets are given. |
||
|---|---|---|
| bin | ||
| contrib/bash_completion.d | ||
| docs | ||
| minimal | ||
| redo | ||
| t | ||
| .gitignore | ||
| .pylintrc | ||
| _all.do | ||
| 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 support for parallel builds, improved logging, 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.
You can subscribe by sending any email message to
redo-list+subscribe@googlegroups.com(note the plus sign).