Roland Ver. 4.5 Informacje Techniczne Pobierz pdf (Strona 18)

8 GNU make

objects = main.o kbd.o command.o display.o \

insert.o search.o files.o utils.o

edit : $(objects)

cc -o edit $(objects)

main.o : defs.h

kbd.o : defs.h command.h

command.o : defs.h command.h

display.o : defs.h buffer.h

insert.o : defs.h buffer.h

search.o : defs.h buffer.h

files.o : defs.h buffer.h command.h

utils.o : defs.h

.PHONY : clean

clean :

rm edit $(objects)

This is how we would write the makeﬁle in actual practice. (The complications associ-

ated with ‘clean’ are described elsewhere. See Section 4.5 [Phony Targets], page 29, and

Section 5.5 [Errors in Recipes], page 49.)

Because implicit rules are so convenient, they are important. You will see them used

frequently.

2.6 Another Style of Makeﬁle

When the objects of a makeﬁle are created only by implicit rules, an alternative style of

makeﬁle is possible. In this style of makeﬁle, you group entries by their prerequisites instead

of by their targets. Here is what one looks like:

objects = main.o kbd.o command.o display.o \

insert.o search.o files.o utils.o

edit : $(objects)

cc -o edit $(objects)

$(objects) : defs.h

kbd.o command.o files.o : command.h

display.o insert.o search.o files.o : buffer.h

Here defs.h is given as a prerequisite of all the object ﬁles; command.h and buffer.h are

prerequisites of the speciﬁc object ﬁles listed for them.

Whether this is better is a matter of taste: it is more compact, but some people dislike

it because they ﬁnd it clearer to put all the information about each target in one place.

1 2 ... 13 14 15 16 17 18 19 20 21 22 23 ... 211 212

Brak uwag

Roland Ver. 4.5 Informacje Techniczne Strona 18