But Now Shhh! company is coming

S by running the C preprocessor, cpp. C compiler to link the program. This rule does the right thing for a simple program with only one source file. It will also do the right thing if there are multiple object files (presumably coming from various other source files), one of which has a name matching that of the executable file. In more complicated cases, such as when there is no object file whose name derives from the executable file name, you must write an explicit recipe for linking. ‘-c’ option. This could be done by using the ‘.o’ object files as intermediates, but it is faster to do the compiling and linking in one step, so that’s how it’s done. The convention of using the same suffix ‘.l’ for all Lex files regardless of whether they produce C code or Ratfor code makes it impossible for make to determine automatically which of the two languages you are using in any particular case. If make is called upon to remake an object file from a ‘.l’ file, it must guess which compiler to use.
The data base output contains file name and line number information for recipe and variable definitions, so it can be a useful debugging tool in complex environments. “Question mode”. Do not run any recipes, or print anything; just return an exit status that is zero if the specified targets are already up to date, one if any remaking is required, or two if an error is encountered. See Instead of Executing Recipes. Eliminate use of the built-in implicit rules (see Using Implicit Rules). You can still define your own by writing pattern rules (see Defining and Redefining Pattern Rules). The ‘-r’ option also clears out the default list of suffixes for suffix rules (see Old-Fashioned Suffix Rules). But you can still define your own suffixes with a rule for .SUFFIXES, and then define your own suffix rules. Note that only rules are affected by the -r option; default variables remain in effect (see Variables Used by Implicit Rules); see the ‘-R’ option below.
Another exception are target-specific variable values. This feature allows you to define different values for the same variable, based on the target that make is currently building. As with automatic variables, these values are only available within the context of a target’s recipe (and in other target-specific assignments). Target-specific variable assignments can be prefixed with any or all of the special keywords export, unexport, override, or private; these apply their normal behavior to this instance of the variable only. Multiple target values create a target-specific variable value for each member of the target list individually. ’). All variables that appear within the variable-assignment are evaluated within the context of the target: thus, any previously-defined target-specific variable values will be in effect. Note that this variable is actually distinct from any “global” value: the two variables do not have to have the same flavor (recursive vs. Target-specific variables have the same priority as any other makefile variable.
Pattern-specific variables are searched after any target-specific variables defined explicitly for that target, and before target-specific variables defined for the parent target. As described in previous sections, make variables are inherited by prerequisites. This capability allows you to modify the behavior of a prerequisite based on which targets caused it to be rebuilt. For example, you might set a target-specific variable on a debug target, then running ‘make debug’ will cause that variable to be inherited by all prerequisites of debug, while just running ‘make all’ (for example) would not have that assignment. Sometimes, however, you may not want a variable to be inherited. For these situations, make provides the private modifier. Although this modifier can be used with any variable assignment, it makes the most sense with target- and pattern-specific variables. Any variable marked private will be visible to its local target but will not be inherited by prerequisites of that target.
If all expansions result in a non-empty string, substitute the expansion of the last condition. See Functions for Conditionals. Compare lhs and rhs numerically; substitute the expansion of lt-part, eq-part, or gt-part depending on whether the left-hand side is less-than, equal-to, or greater-than the right-hand side, respectively. See Functions for Conditionals. 2) with the first, second, etc. See The call Function. Evaluate text then read the results as makefile commands. Expands to the empty string. See The eval Function. Expand the arguments, then open the file filename using mode op and write text to that file. See The file Function. Evaluates to the contents of the variable var, with no expansion performed on it. See The value Function. Here is a summary of the automatic variables. See Automatic Variables, for full information. The file name of the target. The target member name, when the target is an archive member. The name of the first prerequisite. The names of all the prerequisites that are newer than the target, with spaces between them.
Подробнее читайте на: http://news161.ru