home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Fresh Fish 5
/
FreshFish_July-August1994.bin
/
gnu
/
info
/
make.info-5
(
.txt
)
< prev
next >
Wrap
GNU Info File
|
1994-06-22
|
50KB
|
895 lines
This is Info file make.info, produced by Makeinfo-1.54 from the input
file ./make.texinfo.
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.45, last updated 11 May 1994, of `The GNU Make
Manual', for `make', Version 3.71 Beta.
Copyright (C) 1988, '89, '90, '91, '92, '93, '94 Free Software
Foundation, Inc.
Permission is granted to make and distribute verbatim copies of this
manual provided the copyright notice and this permission notice are
preserved on all copies.
Permission is granted to copy and distribute modified versions of
this manual under the conditions for verbatim copying, provided that
the entire resulting derived work is distributed under the terms of a
permission notice identical to this one.
Permission is granted to copy and distribute translations of this
manual into another language, under the above conditions for modified
versions, except that this permission notice may be stated in a
translation approved by the Free Software Foundation.
File: make.info, Node: Options Summary, Prev: Testing, Up: Running
Summary of Options
==================
Here is a table of all the options `make' understands:
These options are ignored for compatibility with other versions of
`make'.
`-C DIR'
`--directory=DIR'
Change to directory DIR before reading the makefiles. If multiple
`-C' options are specified, each is interpreted relative to the
previous one: `-C / -C etc' is equivalent to `-C /etc'. This is
typically used with recursive invocations of `make' (*note
Recursive Use of `make': Recursion.).
`--debug'
Print debugging information in addition to normal processing. The
debugging information says which files are being considered for
remaking, which file-times are being compared and with what
results, which files actually need to be remade, which implicit
rules are considered and which are applied--everything interesting
about how `make' decides what to do.
`--environment-overrides'
Give variables taken from the environment precedence over
variables from makefiles. *Note Variables from the Environment:
Environment.
`-f FILE'
`--file=FILE'
`--makefile=FILE'
Read the file named FILE as a makefile. *Note Writing Makefiles:
Makefiles.
`--help'
Remind you of the options that `make' understands and then exit.
`--ignore-errors'
Ignore all errors in commands executed to remake files. *Note
Errors in Commands: Errors.
`-I DIR'
`--include-dir=DIR'
Specifies a directory DIR to search for included makefiles. *Note
Including Other Makefiles: Include. If several `-I' options are
used to specify several directories, the directories are searched
in the order specified.
`-j [JOBS]'
`--jobs=[JOBS]'
Specifies the number of jobs (commands) to run simultaneously.
With no argument, `make' runs as many jobs simultaneously as
possible. If there is more than one `-j' option, the last one is
effective. *Note Parallel Execution: Parallel, for more
information on how commands are run.
`--keep-going'
Continue as much as possible after an error. While the target that
failed, and those that depend on it, cannot be remade, the other
dependencies of these targets can be processed all the same.
*Note Testing the Compilation of a Program: Testing.
`-l [LOAD]'
`--load-average[=LOAD]'
`--max-load[=LOAD]'
Specifies that no new jobs (commands) should be started if there
are other jobs running and the load average is at least LOAD (a
floating-point number). With no argument, removes a previous load
limit. *Note Parallel Execution: Parallel.
`--just-print'
`--dry-run'
`--recon'
Print the commands that would be executed, but do not execute them.
*Note Instead of Executing the Commands: Instead of Execution.
`-o FILE'
`--old-file=FILE'
`--assume-old=FILE'
Do not remake the file FILE even if it is older than its
dependencies, and do not remake anything on account of changes in
FILE. Essentially the file is treated as very old and its rules
are ignored. *Note Avoiding Recompilation of Some Files: Avoiding
Compilation.
`--print-data-base'
Print the data base (rules and variable values) that results from
reading the makefiles; then execute as usual or as otherwise
specified. This also prints the version information given by the
`-v' switch (see below). To print the data base without trying to
remake any files, use `make -p -f /dev/null'.
`--question'
"Question mode". Do not run any commands, or print anything; just
return an exit status that is zero if the specified targets are
already up to date, one if any remaking is required, or two if an
error is encountered. *Note Instead of Executing the Commands:
Instead of Execution.
`--no-builtin-rules'
Eliminate use of the built-in implicit rules (*note Using Implicit
Rules: Implicit Rules.). You can still define your own by writing
pattern rules (*note Defining and Redefining Pattern Rules:
Pattern Rules.). The `-r' option also clears out the default list
of suffixes for suffix rules (*note Old-Fashioned Suffix Rules:
Suffix Rules.). But you can still define your own suffixes with a
rule for `.SUFFIXES', and then define your own suffix rules.
`--silent'
`--quiet'
Silent operation; do not print the commands as they are executed.
*Note Command Echoing: Echoing.
`--no-keep-going'
`--stop'
Cancel the effect of the `-k' option. This is never necessary
except in a recursive `make' where `-k' might be inherited from
the top-level `make' via `MAKEFLAGS' (*note Recursive Use of
`make': Recursion.) or if you set `-k' in `MAKEFLAGS' in your
environment.
`--touch'
Touch files (mark them up to date without really changing them)
instead of running their commands. This is used to pretend that
the commands were done, in order to fool future invocations of
`make'. *Note Instead of Executing the Commands: Instead of
Execution.
`--version'
Print the version of the `make' program plus a copyright, a list
of authors, and a notice that there is no warranty; then exit.
`--print-directory'
Print a message containing the working directory both before and
after executing the makefile. This may be useful for tracking
down errors from complicated nests of recursive `make' commands.
*Note Recursive Use of `make': Recursion. (In practice, you
rarely need to specify this option since `make' does it for you;
see *Note The `--print-directory' Option: -w Option.)
`--no-print-directory'
Disable printing of the working directory under `-w'. This option
is useful when `-w' is turned on automatically, but you do not
want to see the extra messages. *Note The `--print-directory'
Option: -w Option.
`-W FILE'
`--what-if=FILE'
`--new-file=FILE'
`--assume-new=FILE'
Pretend that the target FILE has just been modified. When used
with the `-n' flag, this shows you what would happen if you were
to modify that file. Without `-n', it is almost the same as
running a `touch' command on the given file before running `make',
except that the modification time is changed only in the
imagination of `make'. *Note Instead of Executing the Commands:
Instead of Execution.
`--warn-undefined-variables'
Issue a warning message whenever `make' sees a reference to an
undefined variable. This can be helpful when you are trying to
debug makefiles which use variables in complex ways.
File: make.info, Node: Implicit Rules, Next: Archives, Prev: Running, Up: Top
Using Implicit Rules
********************
Certain standard ways of remaking target files are used very often.
For example, one customary way to make an object file is from a C
source file using the C compiler, `cc'.
"Implicit rules" tell `make' how to use customary techniques