Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Can you make valid Makefiles without tab characters?

People also ask

Do makefiles need tabs?

Recipes in makefile rules must start with a tab (per definition). If a single tab (interpreted as 8 spaces wide) is not enough to put the recipe clearly indented (meaning at least 4 spaces difference) from the code around it, use additional tabs.

What does $@ mean in Makefiles?

The variable $@ represents the name of the target and $< represents the first prerequisite required to create the output file.

What does all in makefile do?

This means that when you do a "make all", make always thinks that it needs to build it, and so executes all the commands for that target. Those commands will typically be ones that build all the end-products that the makefile knows about, but it could do anything.


This is a syntax oddity/requirement of make, it has nothing to do with Mac OS X. Unfortunately, there's nothing you can do about it if you are going to use make.

Edit: GNU Make now supports a custom recipe prefix. See this answer.

You are not the first one to dislike this aspect of make. To quote Unix Haters' Handbook:

The problem with Dennis’s Makefile is that when he added the comment line, he inadvertently inserted a space before the tab character at the beginning of line 2. The tab character is a very important part of the syntax of Makefiles. All command lines (the lines beginning with cc in our example) must start with tabs. After he made his change, line 2 didn’t, hence the error.

“So what?” you ask, “What’s wrong with that?”

There is nothing wrong with it, by itself. It’s just that when you consider how other programming tools work in Unix, using tabs as part of the syntax is like one of those pungee stick traps in The Green Berets: the poor kid from Kansas is walking point in front of John Wayne and doesn’t see the trip wire. After all, there are no trip wires to watch out for in Kansas corn fields. WHAM!


In the time since this question was originally asked, a version of GNU Make has been released that allows you to use something other than Tab as the prefix character. From the mailing list announcement:

New special variable: .RECIPEPREFIX allows you to reset the recipe introduction character from the default (TAB) to something else. The first character of this variable value is the new recipe introduction character. If the variable is set to the empty string, TAB is used again. It can be set and reset at will; recipes will use the value active when they were first parsed. To detect this feature check the value of $(.RECIPEPREFIX).

This feature was added in GNU Make 3.82, released in July 2010 (six months after this question's original ask date). Since it has in turn been three years and change since that, it's likely that other Make flavors have followed GNU Make.


There is a convoluted way of have a valid makefile without tabs.

If you change your makefile to read:

target: dependencies; command1; command2

If will work. If you want it on more than one line, then you can do:

target: dependencies; \
command1; \
command2

Messy, but it works.


If you have a vimrc in your profile you can add this line to prevent vim from changing to spaces:

autocmd FileType make setlocal noexpandtab

I too was struggling with this, and this fixed it for me. Spread the good word!