News for hackers. Stuff that matters.

A comment on How to Structure C Projects: These Best Practices Worked for Me. Parent comment

Re:How to Structure C Projects: These Best Practices Worked ... by jjgreen on Friday March 08, 2024 @11:12AM (#39642467)
With make, you don't have to install anything, it's POSIX
[ Parent | on HN ]
Re:How to Structure C Projects: These Best Practices Worked ... by yjftsjthsd-h on Friday March 08, 2024 @02:09PM (#39644876)
Being POSIX doesn't mean it's included by default; for example, you can start with the default installation of debian, install a compiler, and still not have make installed
[ Parent | on HN ]
Re:How to Structure C Projects: These Best Practices Worked ... by kerkeslager on Friday March 08, 2024 @04:06PM (#39646501)
This technically isn't true, but I'll give you the point because I don't see `sudo apt install build-essentials` as a significant barrier to entry.

But being able to print "make: ** No targets specified and no makefile found. Stop." to stderr isn't particularly useful, and having to write a Makefile is a significant barrier.

[ Parent | on HN ]