4 ms·
I always put a Makefile in all my projects, especially because I change language often and tooling. I always create a make help task which gives me a list of c
by kuon 4y ago
I always put a Makefile in all my projects, especially because I change language often and tooling.
I always create a make help task which gives me a list of commands and I have a few conventions, make build, make release, make server (dev server). Most of the time the Makefile is very simple and just call npm, cargo, webpack, ...
Being able to enter my blog written in hugo or a phoenix project or a ruby on rails project and just hit make server has been a real help to me.
That being said, I would not use make alone as a build tool for a complex project, it gets very cryptic when complexity is added. But as a "entry point" it serves me well.
- llanowarelves 4y agoThis is the way. I also it use it like that. It is nice to know that i can work on any projects at work and home, and have a consistent dev UX, no matter the toolchain, programming language, etc. A very useful interface that lowers friction.