make-audit VS samurai

Cool!

I also have an experimental (GNU) makefile auditor called "make-audit", available here: https://github.com/david-a-wheeler/make-audit

Per its README: "It will report when an execution of make reads or changes files in ways that are inconsistent with its Makefile. It requires an "auditor" tool named pmaudit in your PATH. It also requires GNU make to be installed and run as make."

Sadly, make-audit is also rather experimental. As I say in its README, "This is an extremely early version. Much needs fixing." For example:

* This doesn't properly handle grouped targets or empty commands. It should handle makefiles with their own SHELL and .ONESHELL values.

* I don't think it handles multi-line make commands exactly correctly (it's close but not quite right).

* Lots more options are needed.

* It needs a better internal test suite.

Still, make-audit does do some useful things, and it'd be awesome if others would be willing to work with me to make it reliably useful.

This is very cool.

A while back I started an experiment/prototype called "make-audit"; this is a (draft) tool to report when an execution of GNU make reads or changes files in ways that are inconsistent with its Makefile: https://github.com/david-a-wheeler/make-audit It's nowhere ready for serious use, but it can detect the following:

* Error: Target TARGET : unreported prerequisites: SET : The make recipe for creating TARGET is reading from the prerequisites in SET, but the makefile fails to report them as dependencies. You may want to add SET to the prerequisites of TARGET.

* Error: Target TARGET : claimed but unused prerequisites: SET : The make recipe for creating TARGET claims that it depends on SET, but the items in SET were never read. You may want to remove SET from the prerequisites of TARGET.

* Error: Target TARGET : unreported target: SET The make recipe for updating TARGET also modifies the files in SET but this is not reported.

* Error: Target TARGET : unmodified reported target: SET

This depended on Poor Man's File Auditor (pmaudit): https://github.com/boyski/pmaudit

Samurai is a faster, drop-in replacement for ninja.

https://github.com/michaelforney/samurai

"If you want to do what "scrappy Google" did these days, then you should use Python + Ninja."

Or, better yet, use a simpler, faster and more portable^1 Ninja written in C.

https://github.com/michaelforney/samurai

1. The "simpler, faster, and more portable", are the author's claims, not mine. I am not the author.

Why is Python not portable, as in, on which systems is "build Python and then use that to run Meson" not a reasonable option?

The CI for boson seems like it runs on platforms where Python definitely is available, but also I notice the CI uses samurai, a reimplementation of ninja with a similar motivation: https://github.com/michaelforney/samurai

Ninja is in C++ so I am even more confused at Sanurai.

Is this just an implementation-diversity thing? (which is great!)

This means ninja is popular both on embedded for its tiny footprint (samurai is about 3k sloc and portable), and for humongous projects like Chrome, because it is infinitely scalable in complexity due to its genaration method.

You could probably post-process samurai (a rewrite of ninja into C) into a single-file: https://github.com/michaelforney/samurai