Re:A Tutorial on Portable Makefiles (2017)
by busfahrer on Monday August 01, 2022 @06:05AM
(#32303908)
I use "just" for this purpose, and I'm very happy with it:
Re:A Tutorial on Portable Makefiles (2017)
by apatheticonion on Thursday August 04, 2022 @08:00PM
(#32349868)
This is great, thank you for the recommendation
Same here. `make test` beats `./gradlew clean test` in one project and `pytest -s ...` in another, etc.
Re:A Tutorial on Portable Makefiles (2017)
by walthamstow on Monday August 01, 2022 @08:57AM
(#32305287)
Yep we use them to run tasks on AWS CodeBuild and Lambda machines.
Make, like vi, has the advantage of just always being there already on whatever machine you need it on.
Me too, I usually have a make “up”, “services” and “test” that do docker “compose up —detach", “docker compose down —volumes” and “rm -rf” temp dirs and run tests with whatever language i’m using. Saves a free brain cycle when switching languages. Sometimes a “data” target for downloading raw data from the internet for stuff like GIS projects.
I never work in C or other languages that actually require the dependency management that make supports.
Re:A Tutorial on Portable Makefiles (2017)
by rsclarke on Monday August 01, 2022 @07:21AM
(#32304446)
https://taskfile.dev/ has been my go to for this.
I use them as cross-platform task runners with commands like "make run-tests" "make run-dev-server". I use it for Go, Rust and even JavaScript (omitting npm scripts).
"make" is an odd keyword for such tasks but there really isn't another simple cross-platform task runner I can use.