3 ms·
If you’re complaining about ./compile or valgrind, you’re soundly in the world of autotools and C compilation. Not make.
by falcolas 4y ago
If you’re complaining about ./compile or valgrind, you’re soundly in the world of autotools and C compilation.
Not make.
- dijit 4y agoThese are just examples of poor portability (thus workarounds) and tools that are not installed when you run `make` as the GP suggested, the claim was that you could write a make file and kinda not have to worry about anything else. Not the case. I could just as easily talk about the pathing issues between MacOS and Linux: or the multiplicity of issues surrounding `sed` (GNU) and `sed` (BSD), or that the `black` python formatter won't be installed by default. It is not as easy as the author claimed, you need whatever dependencies you call on, obviously.