Makefile Generator

Generate a production-ready Makefile from a visual target editor. Define targets with their dependencies and commands, declare variables, and optionally add a .PHONY declaration and a self-documenting help target. Output uses real tab characters for recipe indentation — the most common Makefile mistake is spaces instead of tabs.

How to use the Makefile Generator

Add targets using the + Add target button. For each target:

• Target name — the name you type after make (e.g. build, test, clean).
• Dependencies — space-separated target names or file names that must be built/up-to-date before this target runs (e.g. build test).
• Description — a ##-comment description used by the help target to generate documentation automatically.
• Commands — shell commands to run, one per line. Each becomes a separate recipe line (indented with a real tab). A leading @ suppresses echoing the command.

Add Variables in the textarea (one KEY=value per line) — they are placed at the top of the Makefile. Check Declare .PHONY to mark all non-file targets as phony (prevents conflicts with files of the same name). The self-documenting help target uses grep to extract ## comments and print a usage table when you run make help.

Why Makefiles Use Tabs (and Other Gotchas)

Make is a build automation tool that has been part of Unix since 1976. It reads a Makefile that defines targets, prerequisites (dependencies), and recipes (shell commands). Make's dependency graph tells it which targets are out of date relative to their inputs, so it rebuilds only what has changed. While its original purpose was compiling C programs, it is widely used as a general task runner in any project — Python, Node, Go, Docker, Terraform — because it is universally available and requires no installation.

The single most important and notorious Makefile rule: recipe lines must be indented with a real tab character, not spaces. This is a design decision from 1976 that predates modern editors and has caused decades of frustration. Many editors auto-convert tabs to spaces; make sure yours does not for Makefiles (:set noexpandtab in Vim, the tab handling setting in VS Code). This generator always outputs real tab characters in the recipe lines.

The .PHONY declaration tells Make that certain targets are not files on disk — they are always "out of date" and should always run. Without .PHONY: clean, if a file named clean happens to exist in the directory, make clean will report "nothing to be done" and skip your recipes. The self-documenting help target pattern (grep ## comments) is a popular convention that makes Makefiles discoverable: make help lists available targets with descriptions.

Common use cases

• Project task runners — replace long README command lists with make build, make test, make deploy — consistent across team members and CI.
• Docker workflows — wrap docker build, docker push, and docker compose commands with environment-variable substitution and dependency ordering.
• Infrastructure automation — sequence Terraform init + plan + apply steps with dependency declarations that prevent applying before planning.
• CI/CD pipelines — define pipeline stages as Make targets so developers can reproduce CI steps locally with the same commands.
• Monorepo management — per-service Makefiles with a root Makefile that delegates to subdirectory targets using $(MAKE) -C service-dir build.