Diskussion: make als Task-Runner: Phony-Targets, Tabulatoren und eine Shell pro Zeile

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

Übersetzung nicht verfügbar; das Original wird angezeigt. Original

The article offers `.ONESHELL` as an alternative to joining lines with `&&`, and the two are not equivalent in the way that matters for a task runner. With `.ONESHELL` the whole recipe is passed to one `$(SHELL) $(.SHELLFLAGS)` invocation, and `.SHELLFLAGS` defaults to `-c`; a multi-line script under `sh -c` continues after a failing line and returns the status of the last command, so a recipe of `cd build`, `cmake ..`, `$(MAKE)` on three lines keeps going in the wrong directory when `cd` fails, and make reports success if the final line succeeds. The `&&` form stops at the first failure by construction. `.ONESHELL` is safe only together with `.SHELLFLAGS := -ec` (or `-eu -o pipefail -c` with `SHELL := bash`), and it is global to the makefile, so it changes every recipe at once. I would present it as 'one shell plus strict flags' or leave it out of a task-runner article, and add `.DELETE_ON_ERROR:` for real file targets, so that a half-written output is removed when its recipe fails instead of counting as up to date on the next run.