This is make.info, produced by makeinfo version 4.6 from make.texi. INFO-DIR-SECTION GNU Packages START-INFO-DIR-ENTRY * Make: (make). Remake files automatically. END-INFO-DIR-ENTRY This file documents the GNU Make utility, which determines automatically which pieces of a large program need to be recompiled, and issues the commands to recompile them. This is Edition 0.61, last updated 02 May 2003, of `The GNU Make Manual', for `make', Version 3.81. Copyright 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2002, 2003, 2004 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".  File: make.info, Node: Implicit Rule Search, Prev: Suffix Rules, Up: Implicit Rules Implicit Rule Search Algorithm ============================== Here is the procedure `make' uses for searching for an implicit rule for a target T. This procedure is followed for each double-colon rule with no commands, for each target of ordinary rules none of which have commands, and for each prerequisite that is not the target of any rule. It is also followed recursively for prerequisites that come from implicit rules, in the search for a chain of rules. Suffix rules are not mentioned in this algorithm because suffix rules are converted to equivalent pattern rules once the makefiles have been read in. For an archive member target of the form `ARCHIVE(MEMBER)', the following algorithm is run twice, first using the entire target name T, and second using `(MEMBER)' as the target T if the first run found no rule. 1. Split T into a directory part, called D, and the rest, called N. For example, if T is `src/foo.o', then D is `src/' and N is `foo.o'. 2. Make a list of all the pattern rules one of whose targets matches T or N. If the target pattern contains a slash, it is matched against T; otherwise, against N. 3. If any rule in that list is _not_ a match-anything rule, then remove all nonterminal match-anything rules from the list. 4. Remove from the list all rules with no commands. 5. For each pattern rule in the list: a. Find the stem S, which is the nonempty part of T or N matched by the `%' in the target pattern. b. Compute the prerequisite names by substituting S for `%'; if the target pattern does not contain a slash, append D to the front of each prerequisite name. c. Test whether all the prerequisites exist or ought to exist. (If a file name is mentioned in the makefile as a target or as an explicit prerequisite, then we say it ought to exist.) If all prerequisites exist or ought to exist, or there are no prerequisites, then this rule applies. 6. If no pattern rule has been found so far, try harder. For each pattern rule in the list: a. If the rule is terminal, ignore it and go on to the next rule. b. Compute the prerequisite names as before. c. Test whether all the prerequisites exist or ought to exist. d. For each prerequisite that does not exist, follow this algorithm recursively to see if the prerequisite can be made by an implicit rule. e. If all prerequisites exist, ought to exist, or can be made by implicit rules, then this rule applies. 7. If no implicit rule applies, the rule for `.DEFAULT', if any, applies. In that case, give T the same commands that `.DEFAULT' has. Otherwise, there are no commands for T. Once a rule that applies has been found, for each target pattern of the rule other than the one that matched T or N, the `%' in the pattern is replaced with S and the resultant file name is stored until the commands to remake the target file T are executed. After these commands are executed, each of these stored file names are entered into the data base and marked as having been updated and having the same update status as the file T. When the commands of a pattern rule are executed for T, the automatic variables are set corresponding to the target and prerequisites. *Note Automatic Variables::.  File: make.info, Node: Archives, Next: Features, Prev: Implicit Rules, Up: Top Using `make' to Update Archive Files ************************************ "Archive files" are files containing named subfiles called "members"; they are maintained with the program `ar' and their main use is as subroutine libraries for linking. * Menu: * Archive Members:: Archive members as targets. * Archive Update:: The implicit rule for archive member targets. * Archive Pitfalls:: Dangers to watch out for when using archives. * Archive Suffix Rules:: You can write a special kind of suffix rule for updating archives.  File: make.info, Node: Archive Members, Next: Archive Update, Prev: Archives, Up: Archives Archive Members as Targets ========================== An individual member of an archive file can be used as a target or prerequisite in `make'. You specify the member named MEMBER in archive file ARCHIVE as follows: ARCHIVE(MEMBER) This construct is available only in targets and prerequisites, not in commands! Most programs that you might use in commands do not support this syntax and cannot act directly on archive members. Only `ar' and other programs specifically designed to operate on archives can do so. Therefore, valid commands to update an archive member target probably must use `ar'. For example, this rule says to create a member `hack.o' in archive `foolib' by copying the file `hack.o': foolib(hack.o) : hack.o ar cr foolib hack.o In fact, nearly all archive member targets are updated in just this way and there is an implicit rule to do it for you. *Note:* The `c' flag to `ar' is required if the archive file does not already exist. To specify several members in the same archive, you can write all the member names together between the parentheses. For example: foolib(hack.o kludge.o) is equivalent to: foolib(hack.o) foolib(kludge.o) You can also use shell-style wildcards in an archive member reference. *Note Using Wildcard Characters in File Names: Wildcards. For example, `foolib(*.o)' expands to all existing members of the `foolib' archive whose names end in `.o'; perhaps `foolib(hack.o) foolib(kludge.o)'.  File: make.info, Node: Archive Update, Next: Archive Pitfalls, Prev: Archive Members, Up: Archives Implicit Rule for Archive Member Targets ======================================== Recall that a target that looks like `A(M)' stands for the member named M in the archive file A. When `make' looks for an implicit rule for such a target, as a special feature it considers implicit rules that match `(M)', as well as those that match the actual target `A(M)'. This causes one special rule whose target is `(%)' to match. This rule updates the target `A(M)' by copying the file M into the archive. For example, it will update the archive member target `foo.a(bar.o)' by copying the _file_ `bar.o' into the archive `foo.a' as a _member_ named `bar.o'. When this rule is chained with others, the result is very powerful. Thus, `make "foo.a(bar.o)"' (the quotes are needed to protect the `(' and `)' from being interpreted specially by the shell) in the presence of a file `bar.c' is enough to cause the following commands to be run, even without a makefile: cc -c bar.c -o bar.o ar r foo.a bar.o rm -f bar.o Here `make' has envisioned the file `bar.o' as an intermediate file. *Note Chains of Implicit Rules: Chained Rules. Implicit rules such as this one are written using the automatic variable `$%'. *Note Automatic Variables::. An archive member name in an archive cannot contain a directory name, but it may be useful in a makefile to pretend that it does. If you write an archive member target `foo.a(dir/file.o)', `make' will perform automatic updating with this command: ar r foo.a dir/file.o which has the effect of copying the file `dir/file.o' into a member named `file.o'. In connection with such usage, the automatic variables `%D' and `%F' may be useful. * Menu: * Archive Symbols:: How to update archive symbol directories.  File: make.info, Node: Archive Symbols, Prev: Archive Update, Up: Archive Update Updating Archive Symbol Directories ----------------------------------- An archive file that is used as a library usually contains a special member named `__.SYMDEF' that contains a directory of the external symbol names defined by all the other members. After you update any other members, you need to update `__.SYMDEF' so that it will summarize the other members properly. This is done by running the `ranlib' program: ranlib ARCHIVEFILE Normally you would put this command in the rule for the archive file, and make all the members of the archive file prerequisites of that rule. For example, libfoo.a: libfoo.a(x.o) libfoo.a(y.o) ... ranlib libfoo.a The effect of this is to update archive members `x.o', `y.o', etc., and then update the symbol directory member `__.SYMDEF' by running `ranlib'. The rules for updating the members are not shown here; most likely you can omit them and use the implicit rule which copies files into the archive, as described in the preceding section. This is not necessary when using the GNU `ar' program, which updates the `__.SYMDEF' member automatically.  File: make.info, Node: Archive Pitfalls, Next: Archive Suffix Rules, Prev: Archive Update, Up: Archives Dangers When Using Archives =========================== It is important to be careful when using parallel execution (the `-j' switch; *note Parallel Execution: Parallel.) and archives. If multiple `ar' commands run at the same time on the same archive file, they will not know about each other and can corrupt the file. Possibly a future version of `make' will provide a mechanism to circumvent this problem by serializing all commands that operate on the same archive file. But for the time being, you must either write your makefiles to avoid this problem in some other way, or not use `-j'.  File: make.info, Node: Archive Suffix Rules, Prev: Archive Pitfalls, Up: Archives Suffix Rules for Archive Files ============================== You can write a special kind of suffix rule for dealing with archive files. *Note Suffix Rules::, for a full explanation of suffix rules. Archive suffix rules are obsolete in GNU `make', because pattern rules for archives are a more general mechanism (*note Archive Update::). But they are retained for compatibility with other `make's. To write a suffix rule for archives, you simply write a suffix rule using the target suffix `.a' (the usual suffix for archive files). For example, here is the old-fashioned suffix rule to update a library archive from C source files: .c.a: $(CC) $(CFLAGS) $(CPPFLAGS) -c $< -o $*.o $(AR) r $@ $*.o $(RM) $*.o This works just as if you had written the pattern rule: (%.o): %.c $(CC) $(CFLAGS) $(CPPFLAGS) -c $< -o $*.o $(AR) r $@ $*.o $(RM) $*.o In fact, this is just what `make' does when it sees a suffix rule with `.a' as the target suffix. Any double-suffix rule `.X.a' is converted to a pattern rule with the target pattern `(%.o)' and a prerequisite pattern of `%.X'. Since you might want to use `.a' as the suffix for some other kind of file, `make' also converts archive suffix rules to pattern rules in the normal way (*note Suffix Rules::). Thus a double-suffix rule `.X.a' produces two pattern rules: `(%.o): %.X' and `%.a: %.X'.  File: make.info, Node: Features, Next: Missing, Prev: Archives, Up: Top Features of GNU `make' ********************** Here is a summary of the features of GNU `make', for comparison with and credit to other versions of `make'. We consider the features of `make' in 4.2 BSD systems as a baseline. If you are concerned with writing portable makefiles, you should not use the features of `make' listed here, nor the ones in *Note Missing::. Many features come from the version of `make' in System V. * The `VPATH' variable and its special meaning. *Note Searching Directories for Prerequisites: Directory Search. This feature exists in System V `make', but is undocumented. It is documented in 4.3 BSD `make' (which says it mimics System V's `VPATH' feature). * Included makefiles. *Note Including Other Makefiles: Include. Allowing multiple files to be included with a single directive is a GNU extension. * Variables are read from and communicated via the environment. *Note Variables from the Environment: Environment. * Options passed through the variable `MAKEFLAGS' to recursive invocations of `make'. *Note Communicating Options to a Sub-`make': Options/Recursion. * The automatic variable `$%' is set to the member name in an archive reference. *Note Automatic Variables::. * The automatic variables `$@', `$*', `$<', `$%', and `$?' have corresponding forms like `$(@F)' and `$(@D)'. We have generalized this to `$^' as an obvious extension. *Note Automatic Variables::. * Substitution variable references. *Note Basics of Variable References: Reference. * The command-line options `-b' and `-m', accepted and ignored. In System V `make', these options actually do something. * Execution of recursive commands to run `make' via the variable `MAKE' even if `-n', `-q' or `-t' is specified. *Note Recursive Use of `make': Recursion. * Support for suffix `.a' in suffix rules. *Note Archive Suffix Rules::. This feature is obsolete in GNU `make', because the general feature of rule chaining (*note Chains of Implicit Rules: Chained Rules.) allows one pattern rule for installing members in an archive (*note Archive Update::) to be sufficient. * The arrangement of lines and backslash-newline combinations in commands is retained when the commands are printed, so they appear as they do in the makefile, except for the stripping of initial whitespace. The following features were inspired by various other versions of `make'. In some cases it is unclear exactly which versions inspired which others. * Pattern rules using `%'. This has been implemented in several versions of `make'. We're not sure who invented it first, but it's been spread around a bit. *Note Defining and Redefining Pattern Rules: Pattern Rules. * Rule chaining and implicit intermediate files. This was implemented by Stu Feldman in his version of `make' for AT&T Eighth Edition Research Unix, and later by Andrew Hume of AT&T Bell Labs in his `mk' program (where he terms it "transitive closure"). We do not really know if we got this from either of them or thought it up ourselves at the same time. *Note Chains of Implicit Rules: Chained Rules. * The automatic variable `$^' containing a list of all prerequisites of the current target. We did not invent this, but we have no idea who did. *Note Automatic Variables::. The automatic variable `$+' is a simple extension of `$^'. * The "what if" flag (`-W' in GNU `make') was (as far as we know) invented by Andrew Hume in `mk'. *Note Instead of Executing the Commands: Instead of Execution. * The concept of doing several things at once (parallelism) exists in many incarnations of `make' and similar programs, though not in the System V or BSD implementations. *Note Command Execution: Execution. * Modified variable references using pattern substitution come from SunOS 4. *Note Basics of Variable References: Reference. This functionality was provided in GNU `make' by the `patsubst' function before the alternate syntax was implemented for compatibility with SunOS 4. It is not altogether clear who inspired whom, since GNU `make' had `patsubst' before SunOS 4 was released. * The special significance of `+' characters preceding command lines (*note Instead of Executing the Commands: Instead of Execution.) is mandated by `IEEE Standard 1003.2-1992' (POSIX.2). * The `+=' syntax to append to the value of a variable comes from SunOS 4 `make'. *Note Appending More Text to Variables: Appending. * The syntax `ARCHIVE(MEM1 MEM2...)' to list multiple members in a single archive file comes from SunOS 4 `make'. *Note Archive Members::. * The `-include' directive to include makefiles with no error for a nonexistent file comes from SunOS 4 `make'. (But note that SunOS 4 `make' does not allow multiple makefiles to be specified in one `-include' directive.) The same feature appears with the name `sinclude' in SGI `make' and perhaps others. The remaining features are inventions new in GNU `make': * Use the `-v' or `--version' option to print version and copyright information. * Use the `-h' or `--help' option to summarize the options to `make'. * Simply-expanded variables. *Note The Two Flavors of Variables: Flavors. * Pass command-line variable assignments automatically through the variable `MAKE' to recursive `make' invocations. *Note Recursive Use of `make': Recursion. * Use the `-C' or `--directory' command option to change directory. *Note Summary of Options: Options Summary. * Make verbatim variable definitions with `define'. *Note Defining Variables Verbatim: Defining. * Declare phony targets with the special target `.PHONY'. Andrew Hume of AT&T Bell Labs implemented a similar feature with a different syntax in his `mk' program. This seems to be a case of parallel discovery. *Note Phony Targets: Phony Targets. * Manipulate text by calling functions. *Note Functions for Transforming Text: Functions. * Use the `-o' or `--old-file' option to pretend a file's modification-time is old. *Note Avoiding Recompilation of Some Files: Avoiding Compilation. * Conditional execution. This feature has been implemented numerous times in various versions of `make'; it seems a natural extension derived from the features of the C preprocessor and similar macro languages and is not a revolutionary concept. *Note Conditional Parts of Makefiles: Conditionals. * Specify a search path for included makefiles. *Note Including Other Makefiles: Include. * Specify extra makefiles to read with an environment variable. *Note The Variable `MAKEFILES': MAKEFILES Variable. * Strip leading sequences of `./' from file names, so that `./FILE' and `FILE' are considered to be the same file. * Use a special search method for library prerequisites written in the form `-lNAME'. *Note Directory Search for Link Libraries: Libraries/Search. * Allow suffixes for suffix rules (*note Old-Fashioned Suffix Rules: Suffix Rules.) to contain any characters. In other versions of `make', they must begin with `.' and not contain any `/' characters. * Keep track of the current level of `make' recursion using the variable `MAKELEVEL'. *Note Recursive Use of `make': Recursion. * Provide any goals given on the command line in the variable `MAKECMDGOALS'. *Note Arguments to Specify the Goals: Goals. * Specify static pattern rules. *Note Static Pattern Rules: Static Pattern. * Provide selective `vpath' search. *Note Searching Directories for Prerequisites: Directory Search. * Provide computed variable references. *Note Basics of Variable References: Reference. * Update makefiles. *Note How Makefiles Are Remade: Remaking Makefiles. System V `make' has a very, very limited form of this functionality in that it will check out SCCS files for makefiles. * Various new built-in implicit rules. *Note Catalogue of Implicit Rules: Catalogue of Rules. * The built-in variable `MAKE_VERSION' gives the version number of `make'.  File: make.info, Node: Missing, Next: Makefile Conventions, Prev: Features, Up: Top Incompatibilities and Missing Features ************************************** The `make' programs in various other systems support a few features that are not implemented in GNU `make'. The POSIX.2 standard (`IEEE Standard 1003.2-1992') which specifies `make' does not require any of these features. * A target of the form `FILE((ENTRY))' stands for a member of archive file FILE. The member is chosen, not by name, but by being an object file which defines the linker symbol ENTRY. This feature was not put into GNU `make' because of the nonmodularity of putting knowledge into `make' of the internal format of archive file symbol tables. *Note Updating Archive Symbol Directories: Archive Symbols. * Suffixes (used in suffix rules) that end with the character `~' have a special meaning to System V `make'; they refer to the SCCS file that corresponds to the file one would get without the `~'. For example, the suffix rule `.c~.o' would make the file `N.o' from the SCCS file `s.N.c'. For complete coverage, a whole series of such suffix rules is required. *Note Old-Fashioned Suffix Rules: Suffix Rules. In GNU `make', this entire series of cases is handled by two pattern rules for extraction from SCCS, in combination with the general feature of rule chaining. *Note Chains of Implicit Rules: Chained Rules. * In System V and 4.3 BSD `make', files found by `VPATH' search (*note Searching Directories for Prerequisites: Directory Search.) have their names changed inside command strings. We feel it is much cleaner to always use automatic variables and thus make this feature obsolete. * In some Unix `make's, the automatic variable `$*' appearing in the prerequisites of a rule has the amazingly strange "feature" of expanding to the full name of the _target of that rule_. We cannot imagine what went on in the minds of Unix `make' developers to do this; it is utterly inconsistent with the normal definition of `$*'. * In some Unix `make's, implicit rule search (*note Using Implicit Rules: Implicit Rules.) is apparently done for _all_ targets, not just those without commands. This means you can do: foo.o: cc -c foo.c and Unix `make' will intuit that `foo.o' depends on `foo.c'. We feel that such usage is broken. The prerequisite properties of `make' are well-defined (for GNU `make', at least), and doing such a thing simply does not fit the model. * GNU `make' does not include any built-in implicit rules for compiling or preprocessing EFL programs. If we hear of anyone who is using EFL, we will gladly add them. * It appears that in SVR4 `make', a suffix rule can be specified with no commands, and it is treated as if it had empty commands (*note Empty Commands::). For example: .c.a: will override the built-in `.c.a' suffix rule. We feel that it is cleaner for a rule without commands to always simply add to the prerequisite list for the target. The above example can be easily rewritten to get the desired behavior in GNU `make': .c.a: ; * Some versions of `make' invoke the shell with the `-e' flag, except under `-k' (*note Testing the Compilation of a Program: Testing.). The `-e' flag tells the shell to exit as soon as any program it runs returns a nonzero status. We feel it is cleaner to write each shell command line to stand on its own and not require this special treatment.  File: make.info, Node: Makefile Conventions, Next: Quick Reference, Prev: Missing, Up: Top Makefile Conventions ******************** This node describes conventions for writing the Makefiles for GNU programs. Using Automake will help you write a Makefile that follows these conventions. * Menu: * Makefile Basics:: General Conventions for Makefiles * Utilities in Makefiles:: Utilities in Makefiles * Command Variables:: Variables for Specifying Commands * Directory Variables:: Variables for Installation Directories * Standard Targets:: Standard Targets for Users * Install Command Categories:: Three categories of commands in the `install' rule: normal, pre-install and post-install.  File: make.info, Node: Makefile Basics, Next: Utilities in Makefiles, Up: Makefile Conventions General Conventions for Makefiles ================================= Every Makefile should contain this line: SHELL = /bin/sh to avoid trouble on systems where the `SHELL' variable might be inherited from the environment. (This is never a problem with GNU `make'.) Different `make' programs have incompatible suffix lists and implicit rules, and this sometimes creates confusion or misbehavior. So it is a good idea to set the suffix list explicitly using only the suffixes you need in the particular Makefile, like this: .SUFFIXES: .SUFFIXES: .c .o The first line clears out the suffix list, the second introduces all suffixes which may be subject to implicit rules in this Makefile. Don't assume that `.' is in the path for command execution. When you need to run programs that are a part of your package during the make, please make sure that it uses `./' if the program is built as part of the make or `$(srcdir)/' if the file is an unchanging part of the source code. Without one of these prefixes, the current search path is used. The distinction between `./' (the "build directory") and `$(srcdir)/' (the "source directory") is important because users can build in a separate directory using the `--srcdir' option to `configure'. A rule of the form: foo.1 : foo.man sedscript sed -e sedscript foo.man > foo.1 will fail when the build directory is not the source directory, because `foo.man' and `sedscript' are in the source directory. When using GNU `make', relying on `VPATH' to find the source file will work in the case where there is a single dependency file, since the `make' automatic variable `$<' will represent the source file wherever it is. (Many versions of `make' set `$<' only in implicit rules.) A Makefile target like foo.o : bar.c $(CC) -I. -I$(srcdir) $(CFLAGS) -c bar.c -o foo.o should instead be written as foo.o : bar.c $(CC) -I. -I$(srcdir) $(CFLAGS) -c $< -o $@ in order to allow `VPATH' to work correctly. When the target has multiple dependencies, using an explicit `$(srcdir)' is the easiest way to make the rule work well. For example, the target above for `foo.1' is best written as: foo.1 : foo.man sedscript sed -e $(srcdir)/sedscript $(srcdir)/foo.man > $@ GNU distributions usually contain some files which are not source files--for example, Info files, and the output from Autoconf, Automake, Bison or Flex. Since these files normally appear in the source directory, they should always appear in the source directory, not in the build directory. So Makefile rules to update them should put the updated files in the source directory. However, if a file does not appear in the distribution, then the Makefile should not put it in the source directory, because building a program in ordinary circumstances should not modify the source directory in any way. Try to make the build and installation targets, at least (and all their subtargets) work correctly with a parallel `make'.  File: make.info, Node: Utilities in Makefiles, Next: Command Variables, Prev: Makefile Basics, Up: Makefile Conventions Utilities in Makefiles ====================== Write the Makefile commands (and any shell scripts, such as `configure') to run in `sh', not in `csh'. Don't use any special features of `ksh' or `bash'. The `configure' script and the Makefile rules for building and installation should not use any utilities directly except these: cat cmp cp diff echo egrep expr false grep install-info ln ls mkdir mv pwd rm rmdir sed sleep sort tar test touch true The compression program `gzip' can be used in the `dist' rule. Stick to the generally supported options for these programs. For example, don't use `mkdir -p', convenient as it may be, because most systems don't support it. It is a good idea to avoid creating symbolic links in makefiles, since a few systems don't support them. The Makefile rules for building and installation can also use compilers and related programs, but should do so via `make' variables so that the user can substitute alternatives. Here are some of the programs we mean: ar bison cc flex install ld ldconfig lex make makeinfo ranlib texi2dvi yacc Use the following `make' variables to run those programs: $(AR) $(BISON) $(CC) $(FLEX) $(INSTALL) $(LD) $(LDCONFIG) $(LEX) $(MAKE) $(MAKEINFO) $(RANLIB) $(TEXI2DVI) $(YACC) When you use `ranlib' or `ldconfig', you should make sure nothing bad happens if the system does not have the program in question. Arrange to ignore an error from that command, and print a message before the command to tell the user that failure of this command does not mean a problem. (The Autoconf `AC_PROG_RANLIB' macro can help with this.) If you use symbolic links, you should implement a fallback for systems that don't have symbolic links. Additional utilities that can be used via Make variables are: chgrp chmod chown mknod It is ok to use other utilities in Makefile portions (or scripts) intended only for particular systems where you know those utilities exist.  File: make.info, Node: Command Variables, Next: Directory Variables, Prev: Utilities in Makefiles, Up: Makefile Conventions Variables for Specifying Commands ================================= Makefiles should provide variables for overriding certain commands, options, and so on. In particular, you should run most utility programs via variables. Thus, if you use Bison, have a variable named `BISON' whose default value is set with `BISON = bison', and refer to it with `$(BISON)' whenever you need to use Bison. File management utilities such as `ln', `rm', `mv', and so on, need not be referred to through variables in this way, since users don't need to replace them with other programs. Each program-name variable should come with an options variable that is used to supply options to the program. Append `FLAGS' to the program-name variable name to get the options variable name--for example, `BISONFLAGS'. (The names `CFLAGS' for the C compiler, `YFLAGS' for yacc, and `LFLAGS' for lex, are exceptions to this rule, but we keep them because they are standard.) Use `CPPFLAGS' in any compilation command that runs the preprocessor, and use `LDFLAGS' in any compilation command that does linking as well as in any direct use of `ld'. If there are C compiler options that _must_ be used for proper compilation of certain files, do not include them in `CFLAGS'. Users expect to be able to specify `CFLAGS' freely themselves. Instead, arrange to pass the necessary options to the C compiler independently of `CFLAGS', by writing them explicitly in the compilation commands or by defining an implicit rule, like this: CFLAGS = -g ALL_CFLAGS = -I. $(CFLAGS) .c.o: $(CC) -c $(CPPFLAGS) $(ALL_CFLAGS) $< Do include the `-g' option in `CFLAGS', because that is not _required_ for proper compilation. You can consider it a default that is only recommended. If the package is set up so that it is compiled with GCC by default, then you might as well include `-O' in the default value of `CFLAGS' as well. Put `CFLAGS' last in the compilation command, after other variables containing compiler options, so the user can use `CFLAGS' to override the others. `CFLAGS' should be used in every invocation of the C compiler, both those which do compilation and those which do linking. Every Makefile should define the variable `INSTALL', which is the basic command for installing a file into the system. Every Makefile should also define the variables `INSTALL_PROGRAM' and `INSTALL_DATA'. (The default for `INSTALL_PROGRAM' should be `$(INSTALL)'; the default for `INSTALL_DATA' should be `${INSTALL} -m 644'.) Then it should use those variables as the commands for actual installation, for executables and nonexecutables respectively. Use these variables as follows: $(INSTALL_PROGRAM) foo $(bindir)/foo $(INSTALL_DATA) libfoo.a $(libdir)/libfoo.a Optionally, you may prepend the value of `DESTDIR' to the target filename. Doing this allows the installer to create a snapshot of the installation to be copied onto the real target filesystem later. Do not set the value of `DESTDIR' in your Makefile, and do not include it in any installed files. With support for `DESTDIR', the above examples become: $(INSTALL_PROGRAM) foo $(DESTDIR)$(bindir)/foo $(INSTALL_DATA) libfoo.a $(DESTDIR)$(libdir)/libfoo.a Always use a file name, not a directory name, as the second argument of the installation commands. Use a separate command for each file to be installed.  File: make.info, Node: Directory Variables, Next: Standard Targets, Prev: Command Variables, Up: Makefile Conventions Variables for Installation Directories ====================================== Installation directories should always be named by variables, so it is easy to install in a nonstandard place. The standard names for these variables are described below. They are based on a standard filesystem layout; variants of it are used in SVR4, 4.4BSD, GNU/Linux, Ultrix v4, and other modern operating systems. These two variables set the root for the installation. All the other installation directories should be subdirectories of one of these two, and nothing should be directly installed into these two directories. `prefix' A prefix used in constructing the default values of the variables listed below. The default value of `prefix' should be `/usr/local'. When building the complete GNU system, the prefix will be empty and `/usr' will be a symbolic link to `/'. (If you are using Autoconf, write it as `@prefix@'.) Running `make install' with a different value of `prefix' from the one used to build the program should _not_ recompile the program. `exec_prefix' A prefix used in constructing the default values of some of the variables listed below. The default value of `exec_prefix' should be `$(prefix)'. (If you are using Autoconf, write it as `@exec_prefix@'.) Generally, `$(exec_prefix)' is used for directories that contain machine-specific files (such as executables and subroutine libraries), while `$(prefix)' is used directly for other directories. Running `make install' with a different value of `exec_prefix' from the one used to build the program should _not_ recompile the program. Executable programs are installed in one of the following directories. `bindir' The directory for installing executable programs that users can run. This should normally be `/usr/local/bin', but write it as `$(exec_prefix)/bin'. (If you are using Autoconf, write it as `@bindir@'.) `sbindir' The directory for installing executable programs that can be run from the shell, but are only generally useful to system administrators. This should normally be `/usr/local/sbin', but write it as `$(exec_prefix)/sbin'. (If you are using Autoconf, write it as `@sbindir@'.) `libexecdir' The directory for installing executable programs to be run by other programs rather than by users. This directory should normally be `/usr/local/libexec', but write it as `$(exec_prefix)/libexec'. (If you are using Autoconf, write it as `@libexecdir@'.) Data files used by the program during its execution are divided into categories in two ways. * Some files are normally modified by programs; others are never normally modified (though users may edit some of these). * Some files are architecture-independent and can be shared by all machines at a site; some are architecture-dependent and can be shared only by machines of the same kind and operating system; others may never be shared between two machines. This makes for six different possibilities. However, we want to discourage the use of architecture-dependent files, aside from object files and libraries. It is much cleaner to make other data files architecture-independent, and it is generally not hard. Therefore, here are the variables Makefiles should use to specify directories: `datadir' The directory for installing read-only architecture independent data files. This should normally be `/usr/local/share', but write it as `$(prefix)/share'. (If you are using Autoconf, write it as `@datadir@'.) As a special exception, see `$(infodir)' and `$(includedir)' below. `sysconfdir' The directory for installing read-only data files that pertain to a single machine-that is to say, files for configuring a host. Mailer and network configuration files, `/etc/passwd', and so forth belong here. All the files in this directory should be ordinary ASCII text files. This directory should normally be `/usr/local/etc', but write it as `$(prefix)/etc'. (If you are using Autoconf, write it as `@sysconfdir@'.) Do not install executables here in this directory (they probably belong in `$(libexecdir)' or `$(sbindir)'). Also do not install files that are modified in the normal course of their use (programs whose purpose is to change the configuration of the system excluded). Those probably belong in `$(localstatedir)'. `sharedstatedir' The directory for installing architecture-independent data files which the programs modify while they run. This should normally be `/usr/local/com', but write it as `$(prefix)/com'. (If you are using Autoconf, write it as `@sharedstatedir@'.) `localstatedir' The directory for installing data files which the programs modify while they run, and that pertain to one specific machine. Users should never need to modify files in this directory to configure the package's operation; put such configuration information in separate files that go in `$(datadir)' or `$(sysconfdir)'. `$(localstatedir)' should normally be `/usr/local/var', but write it as `$(prefix)/var'. (If you are using Autoconf, write it as `@localstatedir@'.) `libdir' The directory for object files and libraries of object code. Do not install executables here, they probably ought to go in `$(libexecdir)' instead. The value of `libdir' should normally be `/usr/local/lib', but write it as `$(exec_prefix)/lib'. (If you are using Autoconf, write it as `@libdir@'.) `infodir' The directory for installing the Info files for this package. By default, it should be `/usr/local/info', but it should be written as `$(prefix)/info'. (If you are using Autoconf, write it as `@infodir@'.) `lispdir' The directory for installing any Emacs Lisp files in this package. By default, it should be `/usr/local/share/emacs/site-lisp', but it should be written as `$(prefix)/share/emacs/site-lisp'. If you are using Autoconf, write the default as `@lispdir@'. In order to make `@lispdir@' work, you need the following lines in your `configure.in' file: lispdir='${datadir}/emacs/site-lisp' AC_SUBST(lispdir) `includedir' The directory for installing header files to be included by user programs with the C `#include' preprocessor directive. This should normally be `/usr/local/include', but write it as `$(prefix)/include'. (If you are using Autoconf, write it as `@includedir@'.) Most compilers other than GCC do not look for header files in directory `/usr/local/include'. So installing the header files this way is only useful with GCC. Sometimes this is not a problem because some libraries are only really intended to work with GCC. But some libraries are intended to work with other compilers. They should install their header files in two places, one specified by `includedir' and one specified by `oldincludedir'. `oldincludedir' The directory for installing `#include' header files for use with compilers other than GCC. This should normally be `/usr/include'. (If you are using Autoconf, you can write it as `@oldincludedir@'.) The Makefile commands should check whether the value of `oldincludedir' is empty. If it is, they should not try to use it; they should cancel the second installation of the header files. A package should not replace an existing header in this directory unless the header came from the same package. Thus, if your Foo package provides a header file `foo.h', then it should install the header file in the `oldincludedir' directory if either (1) there is no `foo.h' there or (2) the `foo.h' that exists came from the Foo package. To tell whether `foo.h' came from the Foo package, put a magic string in the file--part of a comment--and `grep' for that string. Unix-style man pages are installed in one of the following: `mandir' The top-level directory for installing the man pages (if any) for this package. It will normally be `/usr/local/man', but you should write it as `$(prefix)/man'. (If you are using Autoconf, write it as `@mandir@'.) `man1dir' The directory for installing section 1 man pages. Write it as `$(mandir)/man1'. `man2dir' The directory for installing section 2 man pages. Write it as `$(mandir)/man2' `...' *Don't make the primary documentation for any GNU software be a man page. Write a manual in Texinfo instead. Man pages are just for the sake of people running GNU software on Unix, which is a secondary application only.* `manext' The file name extension for the installed man page. This should contain a period followed by the appropriate digit; it should normally be `.1'. `man1ext' The file name extension for installed section 1 man pages. `man2ext' The file name extension for installed section 2 man pages. `...' Use these names instead of `manext' if the package needs to install man pages in more than one section of the manual. And finally, you should set the following variable: `srcdir' The directory for the sources being compiled. The value of this variable is normally inserted by the `configure' shell script. (If you are using Autconf, use `srcdir = @srcdir@'.) For example: # Common prefix for installation directories. # NOTE: This directory must exist when you start the install. prefix = /usr/local exec_prefix = $(prefix) # Where to put the executable for the command `gcc'. bindir = $(exec_prefix)/bin # Where to put the directories used by the compiler. libexecdir = $(exec_prefix)/libexec # Where to put the Info files. infodir = $(prefix)/info If your program installs a large number of files into one of the standard user-specified directories, it might be useful to group them into a subdirectory particular to that program. If you do this, you should write the `install' rule to create these subdirectories. Do not expect the user to include the subdirectory name in the value of any of the variables listed above. The idea of having a uniform set of variable names for installation directories is to enable the user to specify the exact same values for several different GNU packages. In order for this to be useful, all the packages must be designed so that they will work sensibly when the user does so.  File: make.info, Node: Standard Targets, Next: Install Command Categories, Prev: Directory Variables, Up: Makefile Conventions Standard Targets for Users ========================== All GNU programs should have the following targets in their Makefiles: `all' Compile the entire program. This should be the default target. This target need not rebuild any documentation files; Info files should normally be included in the distribution, and DVI files should be made only when explicitly asked for. By default, the Make rules should compile and link with `-g', so that executable programs have debugging symbols. Users who don't mind being helpless can strip the executables later if they wish. `install' Compile the program and copy the executables, libraries, and so on to the file names where they should reside for actual use. If there is a simple test to verify that a program is properly installed, this target should run that test. Do not strip executables when installing them. Devil-may-care users can use the `install-strip' target to do that. If possible, write the `install' target rule so that it does not modify anything in the directory where the program was built, provided `make all' has just been done. This is convenient for building the program under one user name and installing it under another. The commands should create all the directories in which files are to be installed, if they don't already exist. This includes the directories specified as the values of the variables `prefix' and `exec_prefix', as well as all subdirectories that are needed. One way to do this is by means of an `installdirs' target as described below. Use `-' before any command for installing a man page, so that `make' will ignore any errors. This is in case there are systems that don't have the Unix man page documentation system installed. The way to install Info files is to copy them into `$(infodir)' with `$(INSTALL_DATA)' (*note Command Variables::), and then run the `install-info' program if it is present. `install-info' is a program that edits the Info `dir' file to add or update the menu entry for the given Info file; it is part of the Texinfo package. Here is a sample rule to install an Info file: $(DESTDIR)$(infodir)/foo.info: foo.info $(POST_INSTALL) # There may be a newer info file in . than in srcdir. -if test -f foo.info; then d=.; \ else d=$(srcdir); fi; \ $(INSTALL_DATA) $$d/foo.info $(DESTDIR)$@; \ # Run install-info only if it exists. # Use `if' instead of just prepending `-' to the # line so we notice real errors from install-info. # We use `$(SHELL) -c' because some shells do not # fail gracefully when there is an unknown command. if $(SHELL) -c 'install-info --version' \ >/dev/null 2>&1; then \ install-info --dir-file=$(DESTDIR)$(infodir)/dir \ $(DESTDIR)$(infodir)/foo.info; \ else true; fi When writing the `install' target, you must classify all the commands into three categories: normal ones, "pre-installation" commands and "post-installation" commands. *Note Install Command Categories::. `uninstall' Delete all the installed files--the copies that the `install' target creates. This rule should not modify the directories where compilation is done, only the directories where files are installed. The uninstallation commands are divided into three categories, just like the installation commands. *Note Install Command Categories::. `install-strip' Like `install', but strip the executable files while installing them. In simple cases, this target can use the `install' target in a simple way: install-strip: $(MAKE) INSTALL_PROGRAM='$(INSTALL_PROGRAM) -s' \ install But if the package installs scripts as well as real executables, the `install-strip' target can't just refer to the `install' target; it has to strip the executables but not the scripts. `install-strip' should not strip the executables in the build directory which are being copied for installation. It should only strip the copies that are installed. Normally we do not recommend stripping an executable unless you are sure the program has no bugs. However, it can be reasonable to install a stripped executable for actual execution while saving the unstripped executable elsewhere in case there is a bug. `clean' Delete all files from the current directory that are normally created by building the program. Don't delete the files that record the configuration. Also preserve files that could be made by building, but normally aren't because the distribution comes with them. Delete `.dvi' files here if they are not part of the distribution. `distclean' Delete all files from the current directory that are created by configuring or building the program. If you have unpacked the source and built the program without creating any other files, `make distclean' should leave only the files that were in the distribution. `mostlyclean' Like `clean', but may refrain from deleting a few files that people normally don't want to recompile. For example, the `mostlyclean' target for GCC does not delete `libgcc.a', because recompiling it is rarely necessary and takes a lot of time. `maintainer-clean' Delete almost everything from the current directory that can be reconstructed with this Makefile. This typically includes everything deleted by `distclean', plus more: C source files produced by Bison, tags tables, Info files, and so on. The reason we say "almost everything" is that running the command `make maintainer-clean' should not delete `configure' even if `configure' can be remade using a rule in the Makefile. More generally, `make maintainer-clean' should not delete anything that needs to exist in order to run `configure' and then begin to build the program. This is the only exception; `maintainer-clean' should delete everything else that can be rebuilt. The `maintainer-clean' target is intended to be used by a maintainer of the package, not by ordinary users. You may need special tools to reconstruct some of the files that `make maintainer-clean' deletes. Since these files are normally included in the distribution, we don't take care to make them easy to reconstruct. If you find you need to unpack the full distribution again, don't blame us. To help make users aware of this, the commands for the special `maintainer-clean' target should start with these two: @echo 'This command is intended for maintainers to use; it' @echo 'deletes files that may need special tools to rebuild.' `TAGS' Update a tags table for this program. `info' Generate any Info files needed. The best way to write the rules is as follows: info: foo.info foo.info: foo.texi chap1.texi chap2.texi $(MAKEINFO) $(srcdir)/foo.texi You must define the variable `MAKEINFO' in the Makefile. It should run the `makeinfo' program, which is part of the Texinfo distribution. Normally a GNU distribution comes with Info files, and that means the Info files are present in the source directory. Therefore, the Make rule for an info file should update it in the source directory. When users build the package, ordinarily Make will not update the Info files because they will already be up to date. `dvi' Generate DVI files for all Texinfo documentation. For example: dvi: foo.dvi foo.dvi: foo.texi chap1.texi chap2.texi $(TEXI2DVI) $(srcdir)/foo.texi You must define the variable `TEXI2DVI' in the Makefile. It should run the program `texi2dvi', which is part of the Texinfo distribution.(1) Alternatively, write just the dependencies, and allow GNU `make' to provide the command. `dist' Create a distribution tar file for this program. The tar file should be set up so that the file names in the tar file start with a subdirectory name which is the name of the package it is a distribution for. This name can include the version number. For example, the distribution tar file of GCC version 1.40 unpacks into a subdirectory named `gcc-1.40'. The easiest way to do this is to create a subdirectory appropriately named, use `ln' or `cp' to install the proper files in it, and then `tar' that subdirectory. Compress the tar file with `gzip'. For example, the actual distribution file for GCC version 1.40 is called `gcc-1.40.tar.gz'. The `dist' target should explicitly depend on all non-source files that are in the distribution, to make sure they are up to date in the distribution. *Note Making Releases: (standards)Releases. `check' Perform self-tests (if any). The user must build the program before running the tests, but need not install the program; you should write the self-tests so that they work when the program is built but not installed. The following targets are suggested as conventional names, for programs in which they are useful. `installcheck' Perform installation tests (if any). The user must build and install the program before running the tests. You should not assume that `$(bindir)' is in the search path. `installdirs' It's useful to add a target named `installdirs' to create the directories where files are installed, and their parent directories. There is a script called `mkinstalldirs' which is convenient for this; you can find it in the Texinfo package. You can use a rule like this: # Make sure all installation directories (e.g. $(bindir)) # actually exist by making them if necessary. installdirs: mkinstalldirs $(srcdir)/mkinstalldirs $(bindir) $(datadir) \ $(libdir) $(infodir) \ $(mandir) or, if you wish to support `DESTDIR', # Make sure all installation directories (e.g. $(bindir)) # actually exist by making them if necessary. installdirs: mkinstalldirs $(srcdir)/mkinstalldirs \ $(DESTDIR)$(bindir) $(DESTDIR)$(datadir) \ $(DESTDIR)$(libdir) $(DESTDIR)$(infodir) \ $(DESTDIR)$(mandir) This rule should not modify the directories where compilation is done. It should do nothing but create installation directories. ---------- Footnotes ---------- (1) `texi2dvi' uses TeX to do the real work of formatting. TeX is not distributed with Texinfo.  File: make.info, Node: Install Command Categories, Prev: Standard Targets, Up: Makefile Conventions Install Command Categories ========================== When writing the `install' target, you must classify all the commands into three categories: normal ones, "pre-installation" commands and "post-installation" commands. Normal commands move files into their proper places, and set their modes. They may not alter any files except the ones that come entirely from the package they belong to. Pre-installation and post-installation commands may alter other files; in particular, they can edit global configuration files or data bases. Pre-installation commands are typically executed before the normal commands, and post-installation commands are typically run after the normal commands. The most common use for a post-installation command is to run `install-info'. This cannot be done with a normal command, since it alters a file (the Info directory) which does not come entirely and solely from the package being installed. It is a post-installation command because it needs to be done after the normal command which installs the package's Info files. Most programs don't need any pre-installation commands, but we have the feature just in case it is needed. To classify the commands in the `install' rule into these three categories, insert "category lines" among them. A category line specifies the category for the commands that follow. A category line consists of a tab and a reference to a special Make variable, plus an optional comment at the end. There are three variables you can use, one for each category; the variable name specifies the category. Category lines are no-ops in ordinary execution because these three Make variables are normally undefined (and you _should not_ define them in the makefile). Here are the three possible category lines, each with a comment that explains what it means: $(PRE_INSTALL) # Pre-install commands follow. $(POST_INSTALL) # Post-install commands follow. $(NORMAL_INSTALL) # Normal commands follow. If you don't use a category line at the beginning of the `install' rule, all the commands are classified as normal until the first category line. If you don't use any category lines, all the commands are classified as normal. These are the category lines for `uninstall': $(PRE_UNINSTALL) # Pre-uninstall commands follow. $(POST_UNINSTALL) # Post-uninstall commands follow. $(NORMAL_UNINSTALL) # Normal commands follow. Typically, a pre-uninstall command would be used for deleting entries from the Info directory. If the `install' or `uninstall' target has any dependencies which act as subroutines of installation, then you should start _each_ dependency's commands with a category line, and start the main target's commands with a category line also. This way, you can ensure that each command is placed in the right category regardless of which of the dependencies actually run. Pre-installation and post-installation commands should not run any programs except for these: [ basename bash cat chgrp chmod chown cmp cp dd diff echo egrep expand expr false fgrep find getopt grep gunzip gzip hostname install install-info kill ldconfig ln ls md5sum mkdir mkfifo mknod mv printenv pwd rm rmdir sed sort tee test touch true uname xargs yes The reason for distinguishing the commands in this way is for the sake of making binary packages. Typically a binary package contains all the executables and other files that need to be installed, and has its own method of installing them--so it does not need to run the normal installation commands. But installing the binary package does need to execute the pre-installation and post-installation commands. Programs to build binary packages work by extracting the pre-installation and post-installation commands. Here is one way of extracting the pre-installation commands: make -n install -o all \ PRE_INSTALL=pre-install \ POST_INSTALL=post-install \ NORMAL_INSTALL=normal-install \ | gawk -f pre-install.awk where the file `pre-install.awk' could contain this: $0 ~ /^\t[ \t]*(normal_install|post_install)[ \t]*$/ {on = 0} on {print $0} $0 ~ /^\t[ \t]*pre_install[ \t]*$/ {on = 1} The resulting file of pre-installation commands is executed as a shell script as part of installing the binary package.  File: make.info, Node: Quick Reference, Next: Error Messages, Prev: Makefile Conventions, Up: Top Quick Reference *************** This appendix summarizes the directives, text manipulation functions, and special variables which GNU `make' understands. *Note Special Targets::, *Note Catalogue of Implicit Rules: Catalogue of Rules, and *Note Summary of Options: Options Summary, for other summaries. Here is a summary of the directives GNU `make' recognizes: `define VARIABLE' `endef' Define a multi-line, recursively-expanded variable. *Note Sequences::. `ifdef VARIABLE' `ifndef VARIABLE' `ifeq (A,B)' `ifeq "A" "B"' `ifeq 'A' 'B'' `ifneq (A,B)' `ifneq "A" "B"' `ifneq 'A' 'B'' `else' `endif' Conditionally evaluate part of the makefile. *Note Conditionals::. `include FILE' `-include FILE' `sinclude FILE' Include another makefile. *Note Including Other Makefiles: Include. `override VARIABLE = VALUE' `override VARIABLE := VALUE' `override VARIABLE += VALUE' `override VARIABLE ?= VALUE' `override define VARIABLE' `endef' Define a variable, overriding any previous definition, even one from the command line. *Note The `override' Directive: Override Directive. `export' Tell `make' to export all variables to child processes by default. *Note Communicating Variables to a Sub-`make': Variables/Recursion. `export VARIABLE' `export VARIABLE = VALUE' `export VARIABLE := VALUE' `export VARIABLE += VALUE' `export VARIABLE ?= VALUE' `unexport VARIABLE' Tell `make' whether or not to export a particular variable to child processes. *Note Communicating Variables to a Sub-`make': Variables/Recursion. `vpath PATTERN PATH' Specify a search path for files matching a `%' pattern. *Note The `vpath' Directive: Selective Search. `vpath PATTERN' Remove all search paths previously specified for PATTERN. `vpath' Remove all search paths previously specified in any `vpath' directive. Here is a summary of the text manipulation functions (*note Functions::): `$(subst FROM,TO,TEXT)' Replace FROM with TO in TEXT. *Note Functions for String Substitution and Analysis: Text Functions. `$(patsubst PATTERN,REPLACEMENT,TEXT)' Replace words matching PATTERN with REPLACEMENT in TEXT. *Note Functions for String Substitution and Analysis: Text Functions. `$(strip STRING)' Remove excess whitespace characters from STRING. *Note Functions for String Substitution and Analysis: Text Functions. `$(findstring FIND,TEXT)' Locate FIND in TEXT. *Note Functions for String Substitution and Analysis: Text Functions. `$(filter PATTERN...,TEXT)' Select words in TEXT that match one of the PATTERN words. *Note Functions for String Substitution and Analysis: Text Functions. `$(filter-out PATTERN...,TEXT)' Select words in TEXT that _do not_ match any of the PATTERN words. *Note Functions for String Substitution and Analysis: Text Functions. `$(sort LIST)' Sort the words in LIST lexicographically, removing duplicates. *Note Functions for String Substitution and Analysis: Text Functions. `$(dir NAMES...)' Extract the directory part of each file name. *Note Functions for File Names: File Name Functions. `$(notdir NAMES...)' Extract the non-directory part of each file name. *Note Functions for File Names: File Name Functions. `$(suffix NAMES...)' Extract the suffix (the last `.' and following characters) of each file name. *Note Functions for File Names: File Name Functions. `$(basename NAMES...)' Extract the base name (name without suffix) of each file name. *Note Functions for File Names: File Name Functions. `$(addsuffix SUFFIX,NAMES...)' Append SUFFIX to each word in NAMES. *Note Functions for File Names: File Name Functions. `$(addprefix PREFIX,NAMES...)' Prepend PREFIX to each word in NAMES. *Note Functions for File Names: File Name Functions. `$(join LIST1,LIST2)' Join two parallel lists of words. *Note Functions for File Names: File Name Functions. `$(word N,TEXT)' Extract the Nth word (one-origin) of TEXT. *Note Functions for File Names: File Name Functions. `$(words TEXT)' Count the number of words in TEXT. *Note Functions for File Names: File Name Functions. `$(wordlist S,E,TEXT)' Returns the list of words in TEXT from S to E. *Note Functions for File Names: File Name Functions. `$(firstword NAMES...)' Extract the first word of NAMES. *Note Functions for File Names: File Name Functions. `$(wildcard PATTERN...)' Find file names matching a shell file name pattern (_not_ a `%' pattern). *Note The Function `wildcard': Wildcard Function. `$(error TEXT...)' When this function is evaluated, `make' generates a fatal error with the message TEXT. *Note Functions That Control Make: Make Control Functions. `$(warning TEXT...)' When this function is evaluated, `make' generates a warning with the message TEXT. *Note Functions That Control Make: Make Control Functions. `$(shell COMMAND)' Execute a shell command and return its output. *Note The `shell' Function: Shell Function. `$(origin VARIABLE)' Return a string describing how the `make' variable VARIABLE was defined. *Note The `origin' Function: Origin Function. `$(foreach VAR,WORDS,TEXT)' Evaluate TEXT with VAR bound to each word in WORDS, and concatenate the results. *Note The `foreach' Function: Foreach Function. `$(call VAR,PARAM,...)' Evaluate the variable VAR replacing any references to `$(1)', `$(2)' with the first, second, etc. PARAM values. *Note The `call' Function: Call Function. `$(eval TEXT)' Evaluate TEXT then read the results as makefile commands. Expands to the empty string. *Note The `eval' Function: Eval Function. `$(value VAR)' Evaluates to the contents of the variable VAR, with no expansion performed on it. *Note The `value' Function: Value Function. Here is a summary of the automatic variables. *Note 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. For prerequisites which are archive members, only the member named is used (*note Archives::). `$^' `$+' The names of all the prerequisites, with spaces between them. For prerequisites which are archive members, only the member named is used (*note Archives::). The value of `$^' omits duplicate prerequisites, while `$+' retains them and preserves their order. `$*' The stem with which an implicit rule matches (*note How Patterns Match: Pattern Match.). `$(@D)' `$(@F)' The directory part and the file-within-directory part of `$@'. `$(*D)' `$(*F)' The directory part and the file-within-directory part of `$*'. `$(%D)' `$(%F)' The directory part and the file-within-directory part of `$%'. `$( tar-`sed -e '/version_string/!d' \ -e 's/[^0-9.]*\([0-9.]*\).*/\1/' \ -e q version.c`.shar.Z dist: $(SRCS) $(AUX) echo tar-`sed \ -e '/version_string/!d' \ -e 's/[^0-9.]*\([0-9.]*\).*/\1/' \ -e q version.c` > .fname -rm -rf `cat .fname` mkdir `cat .fname` ln $(SRCS) $(AUX) `cat .fname` tar chZf `cat .fname`.tar.Z `cat .fname` -rm -rf `cat .fname` .fname tar.zoo: $(SRCS) $(AUX) -rm -rf tmp.dir -mkdir tmp.dir -rm tar.zoo for X in $(SRCS) $(AUX) ; do \ echo $$X ; \ sed 's/$$/^M/' $$X \ > tmp.dir/$$X ; done cd tmp.dir ; zoo aM ../tar.zoo * -rm -rf tmp.dir  File: make.info, Node: GNU Free Documentation License, Next: Concept Index, Prev: Complex Makefile, Up: Top GNU Free Documentation License ****************************** Version 1.1, March 2000 Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. 0. PREAMBLE The purpose of this License is to make a manual, textbook, or other written document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others. This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software. We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference. 1. APPLICABILITY AND DEFINITIONS This License applies to any manual or other work that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language. A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (For example, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them. The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, whose contents can be viewed and edited directly and straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup has been designed to thwart or discourage subsequent modification by readers is not Transparent. A copy that is not "Transparent" is called "Opaque". Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML designed for human modification. Opaque formats include PostScript, PDF, proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML produced by some word processors for output purposes only. The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text. 2. VERBATIM COPYING You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3. You may also lend copies, under the same conditions stated above, and you may publicly display copies. 3. COPYING IN QUANTITY If you publish printed copies of the Document numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects. If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages. If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a publicly-accessible computer-network location containing a complete Transparent copy of the Document, free of added material, which the general network-using public has access to download anonymously at no charge using public-standard network protocols. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public. It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document. 4. MODIFICATIONS You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version: A. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission. B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has less than five). C. State on the Title page the name of the publisher of the Modified Version, as the publisher. D. Preserve all the copyright notices of the Document. E. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices. F. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below. G. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice. H. Include an unaltered copy of this License. I. Preserve the section entitled "History", and its title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence. J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission. K. In any section entitled "Acknowledgments" or "Dedications", preserve the section's title, and preserve in the section all the substance and tone of each of the contributor acknowledgments and/or dedications given therein. L. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles. M. Delete any section entitled "Endorsements". Such a section may not be included in the Modified Version. N. Do not retitle any existing section as "Endorsements" or to conflict in title with any Invariant Section. If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles. You may add a section entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard. You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one. The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version. 5. COMBINING DOCUMENTS You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice. The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work. In the combination, you must combine any sections entitled "History" in the various original documents, forming one section entitled "History"; likewise combine any sections entitled "Acknowledgments", and any sections entitled "Dedications". You must delete all sections entitled "Endorsements." 6. COLLECTIONS OF DOCUMENTS You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects. You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document. 7. AGGREGATION WITH INDEPENDENT WORKS A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, does not as a whole count as a Modified Version of the Document, provided no compilation copyright is claimed for the compilation. Such a compilation is called an "aggregate", and this License does not apply to the other self-contained works thus compiled with the Document, on account of their being thus compiled, if they are not themselves derivative works of the Document. If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one quarter of the entire aggregate, the Document's Cover Texts may be placed on covers that surround only the Document within the aggregate. Otherwise they must appear on covers around the whole aggregate. 8. TRANSLATION Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License provided that you also include the original English version of this License. In case of a disagreement between the translation and the original English version of this License, the original English version will prevail. 9. TERMINATION You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 10. FUTURE REVISIONS OF THIS LICENSE The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See `http://www.gnu.org/copyleft/'. Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation. ADDENDUM: How to use this License for your documents ==================================================== To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page: Copyright (C) YEAR YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. A copy of the license is included in the section entitled ``GNU Free Documentation License''. If you have no Invariant Sections, write "with no Invariant Sections" instead of saying which ones are invariant. If you have no Front-Cover Texts, write "no Front-Cover Texts" instead of "Front-Cover Texts being LIST"; likewise for Back-Cover Texts. If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.  File: make.info, Node: Concept Index, Next: Name Index, Prev: GNU Free Documentation License, Up: Top Index of Concepts ***************** * Menu: * # (comments), in commands: Commands. * # (comments), in makefile: Makefile Contents. * #include: Automatic Prerequisites. * $$@, support for: Automatic Variables. * $, in function call: Syntax of Functions. * $, in rules: Rule Syntax. * $, in variable name: Computed Names. * $, in variable reference: Reference. * %, in pattern rules: Pattern Intro. * %, quoting in patsubst: Text Functions. * %, quoting in static pattern: Static Usage. * %, quoting in vpath: Selective Search. * %, quoting with \ (backslash) <1>: Text Functions. * %, quoting with \ (backslash) <2>: Static Usage. * %, quoting with \ (backslash): Selective Search. * * (wildcard character): Wildcards. * +, and command execution: Instead of Execution. * +, and commands: MAKE Variable. * +, and define: Sequences. * +=: Appending. * +=, expansion: Reading Makefiles. * ,v (RCS file extension): Catalogue of Rules. * - (in commands): Errors. * -, and define: Sequences. * --always-make: Options Summary. * --assume-new <1>: Options Summary. * --assume-new: Instead of Execution. * --assume-new, and recursion: Options/Recursion. * --assume-old <1>: Options Summary. * --assume-old: Avoiding Compilation. * --assume-old, and recursion: Options/Recursion. * --debug: Options Summary. * --directory <1>: Options Summary. * --directory: Recursion. * --directory, and --print-directory: -w Option. * --directory, and recursion: Options/Recursion. * --dry-run <1>: Options Summary. * --dry-run <2>: Instead of Execution. * --dry-run: Echoing. * --environment-overrides: Options Summary. * --file <1>: Options Summary. * --file <2>: Makefile Arguments. * --file: Makefile Names. * --file, and recursion: Options/Recursion. * --help: Options Summary. * --ignore-errors <1>: Options Summary. * --ignore-errors: Errors. * --include-dir <1>: Options Summary. * --include-dir: Include. * --jobs <1>: Options Summary. * --jobs: Parallel. * --jobs, and recursion: Options/Recursion. * --just-print <1>: Options Summary. * --just-print <2>: Instead of Execution. * --just-print: Echoing. * --keep-going <1>: Options Summary. * --keep-going <2>: Testing. * --keep-going: Errors. * --load-average <1>: Options Summary. * --load-average: Parallel. * --makefile <1>: Options Summary. * --makefile <2>: Makefile Arguments. * --makefile: Makefile Names. * --max-load <1>: Options Summary. * --max-load: Parallel. * --new-file <1>: Options Summary. * --new-file: Instead of Execution. * --new-file, and recursion: Options/Recursion. * --no-builtin-rules: Options Summary. * --no-builtin-variables: Options Summary. * --no-keep-going: Options Summary. * --no-print-directory <1>: Options Summary. * --no-print-directory: -w Option. * --old-file <1>: Options Summary. * --old-file: Avoiding Compilation. * --old-file, and recursion: Options/Recursion. * --print-data-base: Options Summary. * --print-directory: Options Summary. * --print-directory, and --directory: -w Option. * --print-directory, and recursion: -w Option. * --print-directory, disabling: -w Option. * --question <1>: Options Summary. * --question: Instead of Execution. * --quiet <1>: Options Summary. * --quiet: Echoing. * --recon <1>: Options Summary. * --recon <2>: Instead of Execution. * --recon: Echoing. * --silent <1>: Options Summary. * --silent: Echoing. * --stop: Options Summary. * --touch <1>: Options Summary. * --touch: Instead of Execution. * --touch, and recursion: MAKE Variable. * --version: Options Summary. * --warn-undefined-variables: Options Summary. * --what-if <1>: Options Summary. * --what-if: Instead of Execution. * -B: Options Summary. * -b: Options Summary. * -C <1>: Options Summary. * -C: Recursion. * -C, and -w: -w Option. * -C, and recursion: Options/Recursion. * -d: Options Summary. * -e: Options Summary. * -e (shell flag): Automatic Prerequisites. * -f <1>: Options Summary. * -f <2>: Makefile Arguments. * -f: Makefile Names. * -f, and recursion: Options/Recursion. * -h: Options Summary. * -I: Options Summary. * -i <1>: Options Summary. * -i: Errors. * -I: Include. * -j <1>: Options Summary. * -j: Parallel. * -j, and archive update: Archive Pitfalls. * -j, and recursion: Options/Recursion. * -k <1>: Options Summary. * -k <2>: Testing. * -k: Errors. * -l: Options Summary. * -l (library search): Libraries/Search. * -l (load average): Parallel. * -m: Options Summary. * -M (to compiler): Automatic Prerequisites. * -MM (to GNU compiler): Automatic Prerequisites. * -n <1>: Options Summary. * -n <2>: Instead of Execution. * -n: Echoing. * -o <1>: Options Summary. * -o: Avoiding Compilation. * -o, and recursion: Options/Recursion. * -p: Options Summary. * -q <1>: Options Summary. * -q: Instead of Execution. * -R: Options Summary. * -r: Options Summary. * -S: Options Summary. * -s <1>: Options Summary. * -s: Echoing. * -t <1>: Options Summary. * -t: Instead of Execution. * -t, and recursion: MAKE Variable. * -v: Options Summary. * -W: Options Summary. * -w: Options Summary. * -W: Instead of Execution. * -w, and -C: -w Option. * -w, and recursion: -w Option. * -W, and recursion: Options/Recursion. * -w, disabling: -w Option. * .a (archives): Archive Suffix Rules. * .C: Catalogue of Rules. * .c: Catalogue of Rules. * .cc: Catalogue of Rules. * .ch: Catalogue of Rules. * .d: Automatic Prerequisites. * .def: Catalogue of Rules. * .dvi: Catalogue of Rules. * .F: Catalogue of Rules. * .f: Catalogue of Rules. * .info: Catalogue of Rules. * .l: Catalogue of Rules. * .LIBPATTERNS, and link libraries: Libraries/Search. * .ln: Catalogue of Rules. * .mod: Catalogue of Rules. * .o: Catalogue of Rules. * .p: Catalogue of Rules. * .PRECIOUS intermediate files: Chained Rules. * .r: Catalogue of Rules. * .S: Catalogue of Rules. * .s: Catalogue of Rules. * .sh: Catalogue of Rules. * .sym: Catalogue of Rules. * .tex: Catalogue of Rules. * .texi: Catalogue of Rules. * .texinfo: Catalogue of Rules. * .txinfo: Catalogue of Rules. * .w: Catalogue of Rules. * .web: Catalogue of Rules. * .y: Catalogue of Rules. * :: rules (double-colon): Double-Colon. * := <1>: Setting. * :=: Flavors. * = <1>: Setting. * =: Flavors. * =, expansion: Reading Makefiles. * ? (wildcard character): Wildcards. * ?= <1>: Setting. * ?=: Flavors. * ?=, expansion: Reading Makefiles. * @ (in commands): Echoing. * @, and define: Sequences. * [...] (wildcard characters): Wildcards. * \ (backslash), for continuation lines: Simple Makefile. * \ (backslash), in commands: Execution. * \ (backslash), to quote % <1>: Text Functions. * \ (backslash), to quote % <2>: Static Usage. * \ (backslash), to quote %: Selective Search. * __.SYMDEF: Archive Symbols. * algorithm for directory search: Search Algorithm. * all (standard target): Goals. * appending to variables: Appending. * ar: Implicit Variables. * archive: Archives. * archive member targets: Archive Members. * archive symbol directory updating: Archive Symbols. * archive, and -j: Archive Pitfalls. * archive, and parallel execution: Archive Pitfalls. * archive, suffix rule for: Archive Suffix Rules. * Arg list too long: Options/Recursion. * arguments of functions: Syntax of Functions. * as <1>: Implicit Variables. * as: Catalogue of Rules. * assembly, rule to compile: Catalogue of Rules. * automatic generation of prerequisites <1>: Automatic Prerequisites. * automatic generation of prerequisites: Include. * automatic variables: Automatic Variables. * automatic variables in prerequisites: Automatic Variables. * backquotes: Shell Function. * backslash (\), for continuation lines: Simple Makefile. * backslash (\), in commands: Execution. * backslash (\), to quote % <1>: Text Functions. * backslash (\), to quote % <2>: Static Usage. * backslash (\), to quote %: Selective Search. * backslashes in pathnames and wildcard expansion: Wildcard Pitfall. * basename: File Name Functions. * binary packages: Install Command Categories. * broken pipe: Parallel. * bugs, reporting: Bugs. * built-in special targets: Special Targets. * C++, rule to compile: Catalogue of Rules. * C, rule to compile: Catalogue of Rules. * cc <1>: Implicit Variables. * cc: Catalogue of Rules. * cd (shell command) <1>: MAKE Variable. * cd (shell command): Execution. * chains of rules: Chained Rules. * check (standard target): Goals. * clean (standard target): Goals. * clean target <1>: Cleanup. * clean target: Simple Makefile. * cleaning up: Cleanup. * clobber (standard target): Goals. * co <1>: Implicit Variables. * co: Catalogue of Rules. * combining rules by prerequisite: Combine By Prerequisite. * command line variable definitions, and recursion: Options/Recursion. * command line variables: Overriding. * commands: Rule Syntax. * commands, backslash (\) in: Execution. * commands, comments in: Commands. * commands, echoing: Echoing. * commands, empty: Empty Commands. * commands, errors in: Errors. * commands, execution: Execution. * commands, execution in parallel: Parallel. * commands, expansion: Shell Function. * commands, how to write: Commands. * commands, instead of executing: Instead of Execution. * commands, introduction to: Rule Introduction. * commands, quoting newlines in: Execution. * commands, sequences of: Sequences. * comments, in commands: Commands. * comments, in makefile: Makefile Contents. * compatibility: Features. * compatibility in exporting: Variables/Recursion. * compilation, testing: Testing. * computed variable name: Computed Names. * conditional expansion: If Function. * conditional variable assignment: Flavors. * conditionals: Conditionals. * continuation lines: Simple Makefile. * controlling make: Make Control Functions. * conventions for makefiles: Makefile Conventions. * ctangle <1>: Implicit Variables. * ctangle: Catalogue of Rules. * cweave <1>: Implicit Variables. * cweave: Catalogue of Rules. * data base of make rules: Options Summary. * deducing commands (implicit rules): make Deduces. * default directories for included makefiles: Include. * default goal <1>: Rules. * default goal: How Make Works. * default makefile name: Makefile Names. * default rules, last-resort: Last Resort. * define, expansion: Reading Makefiles. * defining variables verbatim: Defining. * deletion of target files <1>: Interrupts. * deletion of target files: Errors. * directive: Makefile Contents. * directories, printing them: -w Option. * directories, updating archive symbol: Archive Symbols. * directory part: File Name Functions. * directory search (VPATH): Directory Search. * directory search (VPATH), and implicit rules: Implicit/Search. * directory search (VPATH), and link libraries: Libraries/Search. * directory search (VPATH), and shell commands: Commands/Search. * directory search algorithm: Search Algorithm. * directory search, traditional (GPATH): Search Algorithm. * dist (standard target): Goals. * distclean (standard target): Goals. * dollar sign ($), in function call: Syntax of Functions. * dollar sign ($), in rules: Rule Syntax. * dollar sign ($), in variable name: Computed Names. * dollar sign ($), in variable reference: Reference. * double-colon rules: Double-Colon. * duplicate words, removing: Text Functions. * E2BIG: Options/Recursion. * echoing of commands: Echoing. * editor: Introduction. * Emacs (M-x compile): Errors. * empty commands: Empty Commands. * empty targets: Empty Targets. * environment: Environment. * environment, and recursion: Variables/Recursion. * environment, SHELL in: Execution. * error, stopping on: Make Control Functions. * errors (in commands): Errors. * errors with wildcards: Wildcard Pitfall. * evaluating makefile syntax: Eval Function. * execution, in parallel: Parallel. * execution, instead of: Instead of Execution. * execution, of commands: Execution. * exit status (errors): Errors. * explicit rule, definition of: Makefile Contents. * explicit rule, expansion: Reading Makefiles. * exporting variables: Variables/Recursion. * f77 <1>: Implicit Variables. * f77: Catalogue of Rules. * FDL, GNU Free Documentation License: GNU Free Documentation License. * features of GNU make: Features. * features, missing: Missing. * file name functions: File Name Functions. * file name of makefile: Makefile Names. * file name of makefile, how to specify: Makefile Names. * file name prefix, adding: File Name Functions. * file name suffix: File Name Functions. * file name suffix, adding: File Name Functions. * file name with wildcards: Wildcards. * file name, basename of: File Name Functions. * file name, directory part: File Name Functions. * file name, nondirectory part: File Name Functions. * files, assuming new: Instead of Execution. * files, assuming old: Avoiding Compilation. * files, avoiding recompilation of: Avoiding Compilation. * files, intermediate: Chained Rules. * filtering out words: Text Functions. * filtering words: Text Functions. * finding strings: Text Functions. * flags: Options Summary. * flags for compilers: Implicit Variables. * flavors of variables: Flavors. * FORCE: Force Targets. * force targets: Force Targets. * Fortran, rule to compile: Catalogue of Rules. * functions: Functions. * functions, for controlling make: Make Control Functions. * functions, for file names: File Name Functions. * functions, for text: Text Functions. * functions, syntax of: Syntax of Functions. * functions, user defined: Call Function. * g++ <1>: Implicit Variables. * g++: Catalogue of Rules. * gcc: Catalogue of Rules. * generating prerequisites automatically <1>: Automatic Prerequisites. * generating prerequisites automatically: Include. * get <1>: Implicit Variables. * get: Catalogue of Rules. * globbing (wildcards): Wildcards. * goal: How Make Works. * goal, default <1>: Rules. * goal, default: How Make Works. * goal, how to specify: Goals. * home directory: Wildcards. * IEEE Standard 1003.2: Overview. * ifdef, expansion: Reading Makefiles. * ifeq, expansion: Reading Makefiles. * ifndef, expansion: Reading Makefiles. * ifneq, expansion: Reading Makefiles. * implicit rule: Implicit Rules. * implicit rule, and directory search: Implicit/Search. * implicit rule, and VPATH: Implicit/Search. * implicit rule, definition of: Makefile Contents. * implicit rule, expansion: Reading Makefiles. * implicit rule, how to use: Using Implicit. * implicit rule, introduction to: make Deduces. * implicit rule, predefined: Catalogue of Rules. * implicit rule, search algorithm: Implicit Rule Search. * included makefiles, default directories: Include. * including (MAKEFILE_LIST variable): MAKEFILE_LIST Variable. * including (MAKEFILES variable): MAKEFILES Variable. * including other makefiles: Include. * incompatibilities: Missing. * Info, rule to format: Catalogue of Rules. * install (standard target): Goals. * intermediate files: Chained Rules. * intermediate files, preserving: Chained Rules. * intermediate targets, explicit: Special Targets. * interrupt: Interrupts. * job slots: Parallel. * job slots, and recursion: Options/Recursion. * jobs, limiting based on load: Parallel. * joining lists of words: File Name Functions. * killing (interruption): Interrupts. * last-resort default rules: Last Resort. * ld: Catalogue of Rules. * lex <1>: Implicit Variables. * lex: Catalogue of Rules. * Lex, rule to run: Catalogue of Rules. * libraries for linking, directory search: Libraries/Search. * library archive, suffix rule for: Archive Suffix Rules. * limiting jobs based on load: Parallel. * link libraries, and directory search: Libraries/Search. * link libraries, patterns matching: Libraries/Search. * linking, predefined rule for: Catalogue of Rules. * lint: Catalogue of Rules. * lint, rule to run: Catalogue of Rules. * list of all prerequisites: Automatic Variables. * list of changed prerequisites: Automatic Variables. * load average: Parallel. * loops in variable expansion: Flavors. * lpr (shell command) <1>: Empty Targets. * lpr (shell command): Wildcard Examples. * m2c: Catalogue of Rules. * macro: Using Variables. * make depend: Automatic Prerequisites. * MAKECMDGOALS: Goals. * makefile: Introduction. * makefile name: Makefile Names. * makefile name, how to specify: Makefile Names. * makefile rule parts: Rule Introduction. * makefile syntax, evaluating: Eval Function. * makefile, and MAKEFILES variable: MAKEFILES Variable. * makefile, conventions for: Makefile Conventions. * makefile, how make processes: How Make Works. * makefile, how to write: Makefiles. * makefile, including: Include. * makefile, overriding: Overriding Makefiles. * makefile, parsing: Reading Makefiles. * makefile, remaking of: Remaking Makefiles. * makefile, simple: Simple Makefile. * makefiles, and MAKEFILE_LIST variable: MAKEFILE_LIST Variable. * makefiles, and special variables: Special Variables. * makeinfo <1>: Implicit Variables. * makeinfo: Catalogue of Rules. * match-anything rule: Match-Anything Rules. * match-anything rule, used to override: Overriding Makefiles. * missing features: Missing. * mistakes with wildcards: Wildcard Pitfall. * modified variable reference: Substitution Refs. * Modula-2, rule to compile: Catalogue of Rules. * mostlyclean (standard target): Goals. * multiple rules for one target: Multiple Rules. * multiple rules for one target (::): Double-Colon. * multiple targets: Multiple Targets. * multiple targets, in pattern rule: Pattern Intro. * name of makefile: Makefile Names. * name of makefile, how to specify: Makefile Names. * nested variable reference: Computed Names. * newline, quoting, in commands: Execution. * newline, quoting, in makefile: Simple Makefile. * nondirectory part: File Name Functions. * normal prerequisites: Prerequisite Types. * OBJ: Variables Simplify. * obj: Variables Simplify. * OBJECTS: Variables Simplify. * objects: Variables Simplify. * OBJS: Variables Simplify. * objs: Variables Simplify. * old-fashioned suffix rules: Suffix Rules. * options: Options Summary. * options, and recursion: Options/Recursion. * options, setting from environment: Options/Recursion. * options, setting in makefiles: Options/Recursion. * order of pattern rules: Pattern Intro. * order-only prerequisites: Prerequisite Types. * origin of variable: Origin Function. * overriding makefiles: Overriding Makefiles. * overriding variables with arguments: Overriding. * overriding with override: Override Directive. * parallel execution: Parallel. * parallel execution, and archive update: Archive Pitfalls. * parallel execution, overriding: Special Targets. * parts of makefile rule: Rule Introduction. * Pascal, rule to compile: Catalogue of Rules. * pattern rule: Pattern Intro. * pattern rule, expansion: Reading Makefiles. * pattern rules, order of: Pattern Intro. * pattern rules, static (not implicit): Static Pattern. * pattern rules, static, syntax of: Static Usage. * pattern-specific variables: Pattern-specific. * pc <1>: Implicit Variables. * pc: Catalogue of Rules. * phony targets: Phony Targets. * pitfalls of wildcards: Wildcard Pitfall. * portability: Features. * POSIX: Overview. * POSIX.2: Options/Recursion. * post-installation commands: Install Command Categories. * pre-installation commands: Install Command Categories. * precious targets: Special Targets. * predefined rules and variables, printing: Options Summary. * prefix, adding: File Name Functions. * prerequisite: Rules. * prerequisite pattern, implicit: Pattern Intro. * prerequisite pattern, static (not implicit): Static Usage. * prerequisite types: Prerequisite Types. * prerequisite, expansion: Reading Makefiles. * prerequisites: Rule Syntax. * prerequisites, and automatic variables: Automatic Variables. * prerequisites, automatic generation <1>: Automatic Prerequisites. * prerequisites, automatic generation: Include. * prerequisites, introduction to: Rule Introduction. * prerequisites, list of all: Automatic Variables. * prerequisites, list of changed: Automatic Variables. * prerequisites, normal: Prerequisite Types. * prerequisites, order-only: Prerequisite Types. * prerequisites, varying (static pattern): Static Pattern. * preserving intermediate files: Chained Rules. * preserving with .PRECIOUS <1>: Chained Rules. * preserving with .PRECIOUS: Special Targets. * preserving with .SECONDARY: Special Targets. * print (standard target): Goals. * print target <1>: Empty Targets. * print target: Wildcard Examples. * printing directories: -w Option. * printing of commands: Echoing. * printing user warnings: Make Control Functions. * problems and bugs, reporting: Bugs. * problems with wildcards: Wildcard Pitfall. * processing a makefile: How Make Works. * question mode: Instead of Execution. * quoting %, in patsubst: Text Functions. * quoting %, in static pattern: Static Usage. * quoting %, in vpath: Selective Search. * quoting newline, in commands: Execution. * quoting newline, in makefile: Simple Makefile. * Ratfor, rule to compile: Catalogue of Rules. * RCS, rule to extract from: Catalogue of Rules. * reading makefiles: Reading Makefiles. * README: Makefile Names. * realclean (standard target): Goals. * recompilation: Introduction. * recompilation, avoiding: Avoiding Compilation. * recording events with empty targets: Empty Targets. * recursion: Recursion. * recursion, and -C: Options/Recursion. * recursion, and -f: Options/Recursion. * recursion, and -j: Options/Recursion. * recursion, and -o: Options/Recursion. * recursion, and -t: MAKE Variable. * recursion, and -w: -w Option. * recursion, and -W: Options/Recursion. * recursion, and command line variable definitions: Options/Recursion. * recursion, and environment: Variables/Recursion. * recursion, and MAKE variable: MAKE Variable. * recursion, and MAKEFILES variable: MAKEFILES Variable. * recursion, and options: Options/Recursion. * recursion, and printing directories: -w Option. * recursion, and variables: Variables/Recursion. * recursion, level of: Variables/Recursion. * recursive variable expansion <1>: Flavors. * recursive variable expansion: Using Variables. * recursively expanded variables: Flavors. * reference to variables <1>: Advanced. * reference to variables: Reference. * relinking: How Make Works. * remaking makefiles: Remaking Makefiles. * removal of target files <1>: Interrupts. * removal of target files: Errors. * removing duplicate words: Text Functions. * removing targets on failure: Special Targets. * removing, to clean up: Cleanup. * reporting bugs: Bugs. * rm: Implicit Variables. * rm (shell command) <1>: Errors. * rm (shell command) <2>: Phony Targets. * rm (shell command) <3>: Wildcard Examples. * rm (shell command): Simple Makefile. * rule commands: Commands. * rule prerequisites: Rule Syntax. * rule syntax: Rule Syntax. * rule targets: Rule Syntax. * rule, and $: Rule Syntax. * rule, double-colon (::): Double-Colon. * rule, explicit, definition of: Makefile Contents. * rule, how to write: Rules. * rule, implicit: Implicit Rules. * rule, implicit, and directory search: Implicit/Search. * rule, implicit, and VPATH: Implicit/Search. * rule, implicit, chains of: Chained Rules. * rule, implicit, definition of: Makefile Contents. * rule, implicit, how to use: Using Implicit. * rule, implicit, introduction to: make Deduces. * rule, implicit, predefined: Catalogue of Rules. * rule, introduction to: Rule Introduction. * rule, multiple for one target: Multiple Rules. * rule, no commands or prerequisites: Force Targets. * rule, pattern: Pattern Intro. * rule, static pattern: Static Pattern. * rule, static pattern versus implicit: Static versus Implicit. * rule, with multiple targets: Multiple Targets. * s. (SCCS file prefix): Catalogue of Rules. * SCCS, rule to extract from: Catalogue of Rules. * search algorithm, implicit rule: Implicit Rule Search. * search path for prerequisites (VPATH): Directory Search. * search path for prerequisites (VPATH), and implicit rules: Implicit/Search. * search path for prerequisites (VPATH), and link libraries: Libraries/Search. * searching for strings: Text Functions. * secondary files: Chained Rules. * secondary targets: Special Targets. * sed (shell command): Automatic Prerequisites. * selecting a word: Text Functions. * selecting word lists: Text Functions. * sequences of commands: Sequences. * setting options from environment: Options/Recursion. * setting options in makefiles: Options/Recursion. * setting variables: Setting. * several rules for one target: Multiple Rules. * several targets in a rule: Multiple Targets. * shar (standard target): Goals. * shell command: Simple Makefile. * shell command, and directory search: Commands/Search. * shell command, execution: Execution. * shell command, function for: Shell Function. * shell file name pattern (in include): Include. * shell wildcards (in include): Include. * SHELL, MS-DOS specifics: Execution. * signal: Interrupts. * silent operation: Echoing. * simple makefile: Simple Makefile. * simple variable expansion: Using Variables. * simplifying with variables: Variables Simplify. * simply expanded variables: Flavors. * sorting words: Text Functions. * spaces, in variable values: Flavors. * spaces, stripping: Text Functions. * special targets: Special Targets. * special variables: Special Variables. * specifying makefile name: Makefile Names. * standard input: Parallel. * standards conformance: Overview. * standards for makefiles: Makefile Conventions. * static pattern rule: Static Pattern. * static pattern rule, syntax of: Static Usage. * static pattern rule, versus implicit: Static versus Implicit. * stem <1>: Pattern Match. * stem: Static Usage. * stem, variable for: Automatic Variables. * stopping make: Make Control Functions. * strings, searching for: Text Functions. * stripping whitespace: Text Functions. * sub-make: Variables/Recursion. * subdirectories, recursion for: Recursion. * substitution variable reference: Substitution Refs. * suffix rule: Suffix Rules. * suffix rule, for archive: Archive Suffix Rules. * suffix, adding: File Name Functions. * suffix, function to find: File Name Functions. * suffix, substituting in variables: Substitution Refs. * switches: Options Summary. * symbol directories, updating archive: Archive Symbols. * syntax of rules: Rule Syntax. * tab character (in commands): Rule Syntax. * tabs in rules: Rule Introduction. * TAGS (standard target): Goals. * tangle <1>: Implicit Variables. * tangle: Catalogue of Rules. * tar (standard target): Goals. * target: Rules. * target pattern, implicit: Pattern Intro. * target pattern, static (not implicit): Static Usage. * target, deleting on error: Errors. * target, deleting on interrupt: Interrupts. * target, expansion: Reading Makefiles. * target, multiple in pattern rule: Pattern Intro. * target, multiple rules for one: Multiple Rules. * target, touching: Instead of Execution. * target-specific variables: Target-specific. * targets: Rule Syntax. * targets without a file: Phony Targets. * targets, built-in special: Special Targets. * targets, empty: Empty Targets. * targets, force: Force Targets. * targets, introduction to: Rule Introduction. * targets, multiple: Multiple Targets. * targets, phony: Phony Targets. * terminal rule: Match-Anything Rules. * test (standard target): Goals. * testing compilation: Testing. * tex <1>: Implicit Variables. * tex: Catalogue of Rules. * TeX, rule to run: Catalogue of Rules. * texi2dvi <1>: Implicit Variables. * texi2dvi: Catalogue of Rules. * Texinfo, rule to format: Catalogue of Rules. * tilde (~): Wildcards. * touch (shell command) <1>: Empty Targets. * touch (shell command): Wildcard Examples. * touching files: Instead of Execution. * traditional directory search (GPATH): Search Algorithm. * types of prerequisites: Prerequisite Types. * undefined variables, warning message: Options Summary. * updating archive symbol directories: Archive Symbols. * updating makefiles: Remaking Makefiles. * user defined functions: Call Function. * value: Using Variables. * value, how a variable gets it: Values. * variable: Using Variables. * variable definition: Makefile Contents. * variables: Variables Simplify. * variables, $ in name: Computed Names. * variables, and implicit rule: Automatic Variables. * variables, appending to: Appending. * variables, automatic: Automatic Variables. * variables, command line: Overriding. * variables, command line, and recursion: Options/Recursion. * variables, computed names: Computed Names. * variables, conditional assignment: Flavors. * variables, defining verbatim: Defining. * variables, environment <1>: Environment. * variables, environment: Variables/Recursion. * variables, exporting: Variables/Recursion. * variables, flavors: Flavors. * variables, how they get their values: Values. * variables, how to reference: Reference. * variables, loops in expansion: Flavors. * variables, modified reference: Substitution Refs. * variables, nested references: Computed Names. * variables, origin of: Origin Function. * variables, overriding: Override Directive. * variables, overriding with arguments: Overriding. * variables, pattern-specific: Pattern-specific. * variables, recursively expanded: Flavors. * variables, setting: Setting. * variables, simply expanded: Flavors. * variables, spaces in values: Flavors. * variables, substituting suffix in: Substitution Refs. * variables, substitution reference: Substitution Refs. * variables, target-specific: Target-specific. * variables, unexpanded value: Value Function. * variables, warning for undefined: Options Summary. * varying prerequisites: Static Pattern. * verbatim variable definition: Defining. * vpath: Directory Search. * VPATH, and implicit rules: Implicit/Search. * VPATH, and link libraries: Libraries/Search. * warnings, printing: Make Control Functions. * weave <1>: Implicit Variables. * weave: Catalogue of Rules. * Web, rule to run: Catalogue of Rules. * what if: Instead of Execution. * whitespace, in variable values: Flavors. * whitespace, stripping: Text Functions. * wildcard: Wildcards. * wildcard pitfalls: Wildcard Pitfall. * wildcard, function: File Name Functions. * wildcard, in archive member: Archive Members. * wildcard, in include: Include. * wildcards and MS-DOS/MS-Windows backslashes: Wildcard Pitfall. * word, selecting a: Text Functions. * words, extracting first: Text Functions. * words, filtering: Text Functions. * words, filtering out: Text Functions. * words, finding number: Text Functions. * words, iterating over: Foreach Function. * words, joining lists: File Name Functions. * words, removing duplicates: Text Functions. * words, selecting lists of: Text Functions. * writing rule commands: Commands. * writing rules: Rules. * yacc <1>: Implicit Variables. * yacc <2>: Catalogue of Rules. * yacc: Sequences. * Yacc, rule to run: Catalogue of Rules. * ~ (tilde): Wildcards.  File: make.info, Node: Name Index, Prev: Concept Index, Up: Top Index of Functions, Variables, & Directives ******************************************* * Menu: * $$(@D): Automatic Variables. * $$(@F): Automatic Variables. * $$@: Automatic Variables. * $%: Automatic Variables. * $(%D): Automatic Variables. * $(%F): Automatic Variables. * $(*D): Automatic Variables. * $(*F): Automatic Variables. * $(+D): Automatic Variables. * $(+F): Automatic Variables. * $(.VARIABLES): Special Variables. * $(: Last Resort. * .DEFAULT: Special Targets. * .DEFAULT, and empty commands: Empty Commands. * .DELETE_ON_ERROR <1>: Errors. * .DELETE_ON_ERROR: Special Targets. * .EXPORT_ALL_VARIABLES <1>: Variables/Recursion. * .EXPORT_ALL_VARIABLES: Special Targets. * .IGNORE <1>: Errors. * .IGNORE: Special Targets. * .INTERMEDIATE: Special Targets. * .LIBPATTERNS: Libraries/Search. * .LOW_RESOLUTION_TIME: Special Targets. * .NOTPARALLEL: Special Targets. * .PHONY <1>: Special Targets. * .PHONY: Phony Targets. * .POSIX: Options/Recursion. * .PRECIOUS <1>: Interrupts. * .PRECIOUS: Special Targets. * .SECONDARY: Special Targets. * .SILENT <1>: Echoing. * .SILENT: Special Targets. * .SUFFIXES <1>: Suffix Rules. * .SUFFIXES: Special Targets. * .VARIABLES (list of variables): Special Variables. * /usr/gnu/include: Include. * /usr/include: Include. * /usr/local/include: Include. * < (automatic variable): Automatic Variables. * : Flavors. * MAKE: MAKE Variable. * MAKECMDGOALS: Goals. * makefile: Makefile Names. * Makefile: Makefile Names. * MAKEFILES <1>: Variables/Recursion. * MAKEFILES: MAKEFILES Variable. * MAKEFLAGS: Options/Recursion. * MAKEINFO: Implicit Variables. * MAKELEVEL <1>: Flavors. * MAKELEVEL: Variables/Recursion. * MAKEOVERRIDES: Options/Recursion. * MFLAGS: Options/Recursion. * notdir: File Name Functions. * origin: Origin Function. * OUTPUT_OPTION: Catalogue of Rules. * override: Override Directive. * patsubst <1>: Text Functions. * patsubst: Substitution Refs. * PC: Implicit Variables. * PFLAGS: Implicit Variables. * prefix: Directory Variables. * RFLAGS: Implicit Variables. * RM: Implicit Variables. * sbindir: Directory Variables. * shell: Shell Function. * SHELL: Execution. * SHELL (command execution): Execution. * sort: Text Functions. * strip: Text Functions. * subst <1>: Text Functions. * subst: Multiple Targets. * suffix: File Name Functions. * SUFFIXES: Suffix Rules. * TANGLE: Implicit Variables. * TEX: Implicit Variables. * TEXI2DVI: Implicit Variables. * unexport: Variables/Recursion. * value: Value Function. * vpath: Selective Search. * VPATH: General Search. * vpath: Directory Search. * VPATH: Directory Search. * warning: Make Control Functions. * WEAVE: Implicit Variables. * wildcard <1>: File Name Functions. * wildcard: Wildcard Function. * word: Text Functions. * wordlist: Text Functions. * words: Text Functions. * YACC: Implicit Variables. * YACCR: Implicit Variables. * YFLAGS: Implicit Variables.