6 Commits

Author	SHA1	Message	Date
Michael Forney	24c94be90c	scripts: Check that we got the right number of parameters	2020-01-03 10:53:34 -08:00
Michael Forney	f4720910b9	Update ninja requirement to 1.8.0 and don't bother with atomic outputs ... Since ninja 1.8.0[0] and samurai 0.2[1], output mtime is always recorded after a job succeeds, and outputs are considered dirty if the recorded mtime is older than any input. This means that even if a command partially writes its output then fails (for example, if run with stdout redirected to a file), it will still get re-run during the next build. This means that outputs no longer have to be written atomically (i.e. renamed into place) in order to ensure a correct build, and we can drop the idiom `command >$out.tmp && mv $out.tmp $out`. [0] 04d886b110 [1] 799bc5a471	2019-11-17 15:24:25 -08:00
Michael Forney	10b83649e9	Use source revision in commit message	2019-06-19 12:20:18 -07:00
Michael Forney	680d4261df	scripts/commit.sh: Fix when branch doesn't already exist	2019-04-09 23:02:46 -07:00
Michael Forney	86f67d71e0	scripts/commit.sh: Only commit if tree changed	2019-04-09 20:09:25 -07:00
Michael Forney	741d252822	Port build scripts to POSIX shell ... Since we are now using Lua to generate ninja files, use of rc in build scripts seems unnecessary and adds an additional bootstrap dependency. None of them are too fancy, so just port to POSIX sh instead.	2018-02-16 02:52:34 -08:00