Skip to main content

GNU Make Recursive Wildcard Function

A reader wrote in to ask me about an old message in a mailing list where I'd defined a recursive version of GNU Make's wildcard function.

Unfortunately, there's an error in that message and the correct function is as follows:
rwildcard=$(foreach d,$(wildcard $1*),$(call rwildcard,$d/,$2)
  $(filter $(subst *,%,$2),$d))
Usage is as follows. First, all C files in the current directory (or below).
$(call rwildcard,,*.c)
Then all C files in /tmp:
$(call rwildcard,/tmp/,*.c)
Multiple patterns can be used. Here are all C and H files:
$(call rwildcard,/tmp/,*.c *.h)


Unknown said…
Thank you for posting this, I could not wrap my head around it myself.
Unknown said…
Thank you, this post saved me a lot of headaches.
Alex Cohn said…
Thanks a lot!
Alex Cohn said…
Thanks a lot!
Michel Grosjean said…
Many thanks for this, I was afraid I might have to do something very ugly, but thanks to you I guess I won't :D
Unknown said…
A minor change of the code makes it capabale of searching in a list of base directories:
rwildcard = $(foreach d,$(wildcard $(addsuffix *,$(1))),$(call rwildcard,$(d)/,$(2)) $(filter $(subst *,%,$(2)),$(d)))

The $(addsuffix *,$(1)) instead of $(1)* expands a list of directories in the root invocation into directory candidates for further procesing.

Just a tip: A $(strip ...) around the complete RHS makes it better maintainable in case you want to print the output.
Unknown said…
The archive is available at
Unknown said…
I think that rwildcard should be aligned with original wildcard semantics which accepts the pure file name as pattern. Therefore the improved implementation can look like this:
$(strip $(foreach d,$(wildcard ${1}/*),$(call rwildcard,${d},${2}) $(filter $(subst %%,%,%$(subst *,%,${2})),${d})))

Popular posts from this blog

How to write a successful blog post

First, a quick clarification of 'successful'. In this instance, I mean a blog post that receives a large number of page views. For my, little blog the most successful post ever got almost 57,000 page views. Not a lot by some other standards, but I was pretty happy about it. Looking at the top 10 blog posts (by page views) on my site, I've tried to distill some wisdom about what made them successful. Your blog posting mileage may vary. 1. Avoid using the passive voice The Microsoft Word grammar checker has probably been telling you this for years, but the passive voice excludes the people involved in your blog post. And that includes you, the author, and the reader. By using personal pronouns like I, you and we, you will include the reader in your blog post. When I first started this blog I avoid using "I" because I thought I was being narcissistic. But we all like to read about other people, people help anchor a story in reality. Without people your bl

Your last name contains invalid characters

My last name is "Graham-Cumming". But here's a typical form response when I enter it: Does the web site have any idea how rude it is to claim that my last name contains invalid characters? Clearly not. What they actually meant is: our web site will not accept that hyphen in your last name. But do they say that? No, of course not. They decide to shove in my face the claim that there's something wrong with my name. There's nothing wrong with my name, just as there's nothing wrong with someone whose first name is Jean-Marie, or someone whose last name is O'Reilly. What is wrong is that way this is being handled. If the system can't cope with non-letters and spaces it needs to say that. How about the following error message: Our system is unable to process last names that contain non-letters, please replace them with spaces. Don't blame me for having a last name that your system doesn't like, whose fault is that? Saying "Your

The Elevator Button Problem

User interface design is hard. It's hard because people perceive apparently simple things very differently. For example, take a look at this interface to an elevator: From flickr Now imagine the following situation. You are on the third floor of this building and you wish to go to the tenth. The elevator is on the fifth floor and there's an indicator that tells you where it is. Which button do you press? Most people probably say: "press up" since they want to go up. Not long ago I watched someone do the opposite and questioned them about their behavior. They said: "well the elevator is on the fifth floor and I am on the third, so I want it to come down to me". Much can be learnt about the design of user interfaces by considering this, apparently, simple interface. If you think about the elevator button problem you'll find that something so simple has hidden depths. How do people learn about elevator calling? What's the right amount of