The fact that recipes are not parsed by make, but instead handled by a separate shell process, is central in understanding makefiles. The make program doesn't parse this script: it runs a shell and passes the script to the shell to be run. The recipe is written as a shell script (POSIX sh by default). In addition, each target can have a recipe associated with it which specifies which commands should be invoked to cause that target to be brought up-to-date. The bulk of the file is written in a language that make can understand: this provides variable assignment and expansion, some preprocessor capabilities (including other files, conditional parsing of sections of the file, etc.) as well as the definition of targets and their prerequisites. Makefiles are somewhat unique in a few ways which can be confusing initially.įirst, a makefile consists of two completely different programming languages in the same file. The only way that make determines 'out of date-ness' is by comparing the modification time of target files and their prerequisites. The makefile describes the relationship between targets and prerequisites, and also specifies the commands needed to bring the target up-to-date when one or more of the prerequisites has changed. The make program is typically used to manage the creation of programs from their source files, but it can be more generally used to handle any process where files (or targets) need to be regenerated after other files (or prerequisites) have been modified.

A makefile is a text file which controls the operation of the make program.

How to make makefile for c program