https://github.com/leahneukirchen/redo-c
An implementation of the redo build system in portable C with zero dependencies
https://github.com/leahneukirchen/redo-c
Last synced: over 1 year ago
JSON representation
An implementation of the redo build system in portable C with zero dependencies
- Host: GitHub
- URL: https://github.com/leahneukirchen/redo-c
- Owner: leahneukirchen
- Created: 2015-09-01T14:11:12.000Z (almost 11 years ago)
- Default Branch: master
- Last Pushed: 2023-09-29T13:22:37.000Z (almost 3 years ago)
- Last Synced: 2024-05-10T00:27:54.522Z (about 2 years ago)
- Language: C
- Size: 34.2 KB
- Stars: 102
- Watchers: 7
- Forks: 12
- Open Issues: 11
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
- awesome-tools - leahneukirchen/redo-c - An implementation of the redo build system in portable C with zero dependencies (Process Manager / Selfhosted)
README
# redo-c
redo-c is an implementation of the redo build system (designed by
Daniel J. Bernstein) in portable C with zero external dependencies.
## Documentation
Please refer to the documentation for
[redo in Python](https://github.com/apenwarr/redo/blob/master/README.md),
or the [tutorial by Jonathan de Boyne Pollard](http://jdebp.info/FGA/introduction-to-redo.html)
for usage instructions.
## Notes about the redo-c implementation of redo
* Without arguments, `redo` behaves like `redo all`.
* `.do` files always are executed in their directory, arguments are
relative paths.
* Standard output of `.do` files is only captured as build product if
`redo -s` is used, or the environment variable `REDO_STDOUT` is set to 1.
Else, standard output is simply displayed.
* Non-executable `.do` files are run with `/bin/sh -e`.
`redo -x` can be utilized to use `/bin/sh -e -x` instead, for
debugging `.do` files or verbose builds.
* Executable `.do` files are simply executed, and should have a shebang line.
* When a target makes no output, no target file is created. The target
is considered always out of date.
* `default.do` files are checked in all parent directories up to `/`.
* Parallel builds can be started with `redo -j N` (or `JOBS=N redo`),
this uses a job broker similar to but not compatible with GNU make.
* To detect whether a file has changed, we first compare `ctime` and
in case it differs, a SHA2 hash of the contents.
* Dependencies are tracked in `.dep.BASENAME` files all over the tree.
This is an implementation detail.
* Builds can be started from every directory and should yield same results.
* `redo -f` will consider all targets outdated and force a rebuild.
* `redo -k` will keep going if a target failed to build.
## Copying
To the extent possible under law, Leah Neukirchen
has waived all copyright and related or neighboring rights to this work.
http://creativecommons.org/publicdomain/zero/1.0/