Question 1

How do I install Mmake on Windows?

Accepted Answer

Mmake is built with Go, so you can install it via gobinaries.com with a curl command or compile from source using `go get`. However, the README primarily focuses on Unix-like systems, so Windows users might need to adapt the installation steps or use WSL.

Question 2

Is Mmake secure for downloading remote Makefiles?

Accepted Answer

There are security risks as remote includes execute code from external URLs. The README advises forking repositories to maintain control, but this requires manual oversight and doesn't eliminate all vulnerabilities, especially in automated environments.

Question 3

Mmake vs Make: which is better for task automation?

Accepted Answer

Mmake enhances Make with features like help output and remote includes, making it better for teams already using Make who want improved documentation and reuse. However, if you need a simpler, more secure task runner, alternatives like Just might be preferable.

Question 4

Can I use Mmake in a CI/CD pipeline?

Accepted Answer

Yes, but you must install Mmake in the build environment and set up the alias. Remote includes might cause network dependencies or security concerns, so cache them or use forked copies to ensure reliability.

Question 5

How to update remote includes in Mmake?

Accepted Answer

Use the `make update` command provided by Mmake, which re-downloads remote includes to get the latest versions. This is documented in the 'Update' subsection, but it requires manual execution and internet connectivity.

Question 6

What are good alternatives to Mmake for modern task running?

Accepted Answer

Alternatives include standalone task runners like Task, Just, or npm scripts for Node projects, which offer simpler syntax and better security out-of-the-box, but lack Mmake's direct compatibility with existing Makefiles.

mmake

Overview

Use Cases

Not Ideal For

Pros & Cons

Pros

Related Projects

Found a gem we're missing?

Cons

Frequently Asked Questions