Makefile tutorial 2019-11-25
When evaluating peers, I see many Makefiles which look something like this:
NAME = ft_foo SRCS = ft_bar.c ft_baz.c FLAGS = -Wall -Wextra -Werror all: $(NAME) $(NAME): gcc $(FLAGS) -o $(NAME) $(SRCS) clean: rm -f *.o fclean: clean rm -f $(NAME) re: fclean all
While this is valid, it is possible to do much more with
make. When we finish
this tutorial, typing
make will only recompile the source files you changed.
make re is never needed, and
make will be much quicker.
A basic Makefile
First off, let’s make a very basic
Makefile, it will not be norm compliant,
we will worry about that later.
Clone this repository containing an example project:
git clone https://git.sr.ht/~nloomans/makefile-tutorial
Makefile in the repository is as follows:
foo: main.o greeter.o gcc -o $@ $^ %.o: %.c gcc -c -Wall -Wextra -Werror -o $@ $< clean: rm -f foo main.o greeter.o
Let’s go through what is happening here. The first rule is
foo. This rule has
greeter.o, which are compiled from
greeter.c, respectively, but
make doesn’t know that yet. When
these dependencies, it will look rule by rule to see which rule can create that
file. In this case the rule
%.o satisfies both
%.o: %.c rule means that for any
.o file, we are depending on a
file with the same name. If the object file doesn’t exist or if the source file
is newer then the object file, the contents of the rule will be executed. The
recipe (rule contents) contains two special variables.
$@ stands for the
target, for example,
$< stands for the first dependency,
main.c. In summary, this rule states that any object file will
be compiled using the corresponding source file, using the
gcc -c command.
If either the
main.o or the
greeter.o rule was run, the
foo rule will
also execute. Now that the object files have been compiled we can link them
into an executable.
$^ is similar to
$^ stands for all the
$< will only get the first one.
makeand observe all of the files being compiled and then linked. Change one
.cfile and observe only that
.cfill being recompiled followed by linking. Change nothing and run
makeagain, observe that nothing happens. (If it did link after changing nothing, that would be relinking and therefore a norm error.)
Exercise: Compile a single object file, without linking them to
foo. You may only use the
makecommand and you may not edit the Makefile.
Exercise: Try adding a
exercise: exercise.o greeter.orule. You should create an
exercise.cfile which uses a function defined in
Let’s modify the
Makefile. The new contents will look like this:
NAME = foo OBJ_FILES = main.o greeter.o CFLAGS = -Wall -Wextra -Werror $(NAME): $(OBJ_FILES) $(CC) -o $@ $^ %.o: %.c $(CC) -c $(CFLAGS) -o $@ $< clean: rm -f $(NAME) $(OBJ_FILES)
If you are getting a
Makefile:8: *** missing separator. Stop.error, that means the rules you copied have been indented using spaces instead of tabs.
Makefilerules are required to be indented using tabs, changing the spaces to tabs manually will fix the issue.
First off, there is no such thing as
gcc on the Codam iMacs. The actual
compiler installed is
clang is mostly compatible with
gcc, and a
lot of programs only compile with
gcc even though they are also able to
be compiled using
clang. As a compatibility layer for these programs an
alias has been installed in
/usr/bin/gcc, but in reality, you are executing
A nicer solution for this is to use
cc. When using
cc you will use the
preferred compiler for the current operating system. On Linux systems, this will
most likely be
gcc. And on macOS systems, this will most likely be
However, you may want to use
clang when compiling on Linux, or
compiling on macOS. For this,
$(CC). By default,
cc. However, it is possible to overwrite this and compile using
whatever compiler you want by either setting the
CC environment variable or
by compiling like so:
$(CFLAGS) make variable is the standard variable for setting the compile
flags. Notice how we didn’t use it in the linking step. This is because these
compile flags only apply during the compilation stage. While it is possible to
add them to the linking stage, as long as you don’t have any
.c files it the
list they will be ignored. Defining them like this allows us to easily modify
$(CFLAGS) when compiling. For example, we might want to use
make "CFLAGS=-Wall -Wextra -Werror -g" to generate debug information. Or we
might want to compile using
make "CFLAGS=-Wall -Wextra -Werror -O2" to create
an optimized production build.
Exercise: Try to recompile with the
-pedanticcompile flag. Try changing the name of the executable name. Do this without modifying the Makefile.
Recompiling when your headers change
We are missing one last piece of the puzzle for a really nice Makefile. Right
now, when you change a header file the object files will not be recompiled.
This can result in strange errors if you forget to run
make re. One way to
solve this is by telling
make the object files are dependent on the header
HEADER_FILES = greeter.h %.o: %.c $(HEADER_FILES) $(CC) -c $(CFLAGS) -o $@ $<
This rule now means that
main.o is dependent on
greeter.o is dependent on
run a rule if any of the dependencies are newer then the target,
automatically recreate all object files if any header file changes.
Exercise: Why are we using
$^here? Why doesn’t
$^work in this situation?
We need a few more rules to get full norm compliance.
NAME = foo OBJ_FILES = main.o greeter.o HEADER_FILES = greeter.h CFLAGS = -Wall -Wextra -Werror all: $(NAME) $(NAME): $(OBJ_FILES) $(CC) -o $@ $^ %.o: %.c $(HEADER_FILES) $(CC) -c $(CFLAGS) -o $@ $< clean: rm -f $(OBJ_FILES) fclean: clean rm -f $(NAME) re: fclean all .PHONY: all clean fclean re
all rule itself has no special meaning. Make simply runs the first rule
when no rule is specified. The
.PHONY line means that all of these rules
should be treated like commands, not outputs. So even if there exists a file
clean, clean will still run.
The following subjects are advanced ways to improve your Makefile further. Please read on if you are curious, but you don’t have to.
Make has an awesome option called
-j, which will allow multi-threading. If
make -j6 to compile your project, up to 6 rules can be run at the
same time. This is very nice since it makes your
Makefile much faster.
Especially on bigger projects!
Unfortunately, this means that we can no longer depend on the order of
dependencies. This breaks the
re target. Since both the
fclean and the
all dependencies are run at the same time, files will be deleted during
compilation. This will well… break everything. One solution is to redefine
re rule as follows:
re: $(MAKE) fclean $(MAKE) all
Instead of having
all as dependencies we will recursively call
make twice. The
$(MAKE) rule will expand to a
make with all of the flags
used to call the parent
make pre-set. For example, if we run
make CC=clang re,
$(NAME) will expand to
make CC=clang. We will first
make again using fclean, wait until it has finished, and then call
all. Now we can run
make re -j6 with peace.
The bonus target
bonus target is quite hard to get right. Because the target name does not
equal to the output file (e.g.
libft.a), make will always recompile bonus.
Even if you didn’t change anything. A better way to handle this is by adding a
WITH_BONUS variable to make. Let me demonstrate:
(this isn’t valid right now, we still need a bonus rule. I’ll get back to you on that one later in this document.)
NAME=foo REG_OBJ_FILES = main.o greeter.o BONUS_OBJ_FILES = loud_greeter_bonus.o HEADER_FILES = greeter.h CFLAGS = -Wall -Wextra -Werror ifdef WITH_BONUS OBJ_FILES = $(REG_OBJ_FILES) $(BONUS_OBJ_FILES) else OBJ_FILES = $(REG_OBJ_FILES) endif all: $(NAME) $(NAME): $(OBJ_FILES) $(CC) -o $@ $^ %.o: %.c $(HEADER_FILES) $(CC) -c $(CFLAGS) -o $@ $< clean: rm -f $(REG_OBJ_FILES) $(BONUS_OBJ_FILES) fclean: clean rm -f $(NAME) re: $(MAKE) fclean $(MAKE) all .PHONY: all clean fclean re
By default, the
$(OBJ_FILES) variable is only equal to the non-bonus object
files. However, if we compile using
$(OBJ_FILES) will be
equal to all files, including the bonus ones. If we first compile only the
regular files, and then compile with the bonus files extra, this Makefile will
only recompile the bonus source files. And, most importantly, running
make WITH_BONUS=1 with nothing change will do nothing!
However, we still need the
bonus target, unfortunately. One way to solve this
would be by calling
make again while inside of the
Makefile. Like this:
bonus: $(MAKE) WITH_BONUS=1 all
This is all a bit clunky, and I hope the
will be updated to use a separate
libftbonus.a target, but this is the best
we can do now.
Articles from blogs I follow
My favorite operating system is Plan 9 from Bell Labs. The simplicity and cohesive design throughout really stands out. In my opinion, Plan 9 is much, much better than any other operating system I’ve used, and I’ve used a lot of operating systems. Plan 9 is …via Blogs on Sourcehut 2020-05-11
Tim Bray’s excellent “Bye Amazon” post inspired me to take this article off of my backlog, where it has been sitting for a few weeks. I applaud Tim for stepping down from a company that has demonstrated itself incompatible with his sense of right and wrong, …via Drew DeVault's Blog 2020-05-05
What a response! I want to start with an enormous thank you to the thousands of Go developers who participated in this year’s survey. For 2019, we saw 10,975 responses, nearly twice as many as last year! On behalf of the rest of the team, I …via The Go Programming Language Blog 2020-04-20
Generated by openring