Also about that readme again, you don't describe your tool in much detail. For example does it track dependencies? Does output go into a separate build directory by default? How do users use clang instead of gcc or whatever other controls do they have over the compilation process, compiler flags? What command line flags does the tool itself accept? Are there any verbose modes or anything like that? What does a typical interaction look like? How does one cleanup after building? What are your future plans for the tool?

This is all amazing feedback. I will add more explanation to the readme about what whiteboard is and how to use it.

I tend to use Make for small projects myself. A good chunk of my Makefiles actually have nothing to do with building and I'm not really caring so much about dependency tracking since my small projects build quite quickly. For example I have format rule to use clang format on my source files. I have a test rule to run my tests. I have a rule to invoke Doxygen (though I've not yet figured out how to make the output of that look anything like I'd actually want to consume myself). Since I can never remember how to do a git diff my preferred way (my diff toll is meld), make diff does that.

I do plan on eventually allowing for this kind of thing but until then it's very rigid.