Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I understand that people need resources to understand the Makefiles of existing projects, but I fear that tutorials might encourage people to use Make in new projects. Yes, I really want to extinguish Make. Other build tools are also "bad" but Make deserves a special place in hell.


Been using Make for decades, I don't see the problem. It works sufficiently well to be in use in a lot of my projects as a comfortable and productive environment. As with all 'tool X must die' conversations, one must always end with the only relevant conclusion that should be made: ymmv.


In this case, there are genuinly better options.

CMake, for example, is less arcane, and can also generate project files for visual studio.

I'd agree that make shouldn't really be the go-to choice for brand new projects. It's limitations can encircle new projects.


CMake generates makefiles, at least as I have used it, so you need to understand makefiles to debug any build problems.


It's true, but it has the benefit that your makefiles are now complient with every other cmake users makefiles, and not special snowflakes. That makes it more likely that someone has already had your problem and posted a turnkey solution.


CMake, less arcane? Surely you're jokin.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: