Why should I avoid shell loops in Makefiles for subdirectories?

Shell loops execute sub-makes serially, which ignores the -j parallel flag, breaks the -k continue-on-error behavior, and requires manual error handling like '|| exit 1'.

Why use $(MAKE) instead of just typing 'make' in a rule?

Using the $(MAKE) variable ensures that top-level flags, such as -n (dry run), -j (parallel), and -q (question), are correctly passed down to all recursive child processes.

How can I share variables between the root and subdirectory Makefiles?

You can use the 'export' directive for specific variables, pass them as command-line arguments to the sub-make, or use .EXPORT_ALL_VARIABLES for broader scope.

How does this skill improve build performance?

By implementing the phony target pattern, GNU Make can schedule and build independent subdirectories in parallel, often resulting in 4x to 8x speed improvements on multi-core systems.

Recursive Multi-Directory Make

Name: Recursive Multi-Directory Make
Author: therealbill

bytherealbill

0•

Deployment & DevOps

Optimizes multi-directory GNU Make builds by replacing inefficient shell loops with high-performance phony target patterns.

The Recursive Multi-Directory Make skill streamlines the management of complex projects spread across multiple folders by implementing robust build patterns. By advocating for the phony target pattern over traditional shell loops, it enables full support for parallel execution via the -j flag, proper error propagation with the -k flag, and cleaner project organization. This skill provides expert guidance on correctly exporting variables to sub-makes, using the $(MAKE) variable for consistent flag passing, and defining explicit dependencies between subdirectories to ensure reliable, high-speed build pipelines.

Key Features

01Guides correct variable exporting and $(MAKE) recursive usage

02Automates dependency management between complex project subdirectories

030 GitHub stars

04Replaces serial shell loops with parallelizable phony target patterns

05Ensures proper error propagation and make -k continue-on-error support

06Enables full support for make -j flags for significantly faster builds

Use Cases

01Optimizing build times for large C/C++, Go, or Rust projects with many sub-packages

02Standardizing CI/CD build scripts for reliable error reporting and performance

03Refactoring monolithic Makefiles into modular, multi-directory structures

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add therealbill/mynet makefile-recursive-multi-directory

For use in Claude.ai and ChatGPT

Download Skill