345ocs-000Docs-000D.xmlMakefiles › Makefile syntaxIt is common practice to copy and modify old makefules rather than generating new ones from scratch.Context346ocs-000Bocs-000B.xmlMakefilesNote2024913A well written makefile describes all the files and settings used to compile a project and link it with the appropriate librariesManaging a build with a makefile is less error-prone and far simpler after a _one-time setup cost_. A makefile with a proper dependency graph will only rebuild a target when one or more of the components it depends on has changed. This allows seperating the components of a project whcih can be built independently.257ocs-000Docs-000D.xmlMakefile syntaxIt is common practice to copy and modify old makefules rather than generating new ones from scratch.258ocs-000Eocs-000E.xmlMakefile macrosSubsitutions defined toward top of the file, e.g. (CFLAGS = -g -Wall), and are similar to #define in C . It can be referenced later with $(CFLAGS).Example macros: - OBJECTS = $(SOURCES:.c=o) - Defines the OBJECTS macro to be the same as the SOURCES macro except that every instance of .c is replaced with .o. - $@: - built-in, name of the current target - $^: - built-in, current targets list of dependencies259ocs-000Focs-000F.xmlTargetsWritten in the following formwhere the target name is the name of the file that will be produced when this target is built. The first target listed in a make file is the default target, meaning it is invoked by make with no args.260ocs-000Cocs-000C.xmlPhony targetsThe clean target in the example does not fit the pattern which is previously described of targets. It does not create a file named clean, rather it is a shortcut for running a command whcih cclears out the projects build files. These commands are listed as dependencies of .PHONY which allows Make to run the target without any dependency checks.linkscs107 makefile guide Makefile basics - gist