BSDMAKE(1) BSD General Commands Manual BSDMAKE(1)
NAME
bbssddmmaakkee - maintain program dependencies
SYNOPSIS
bbssddmmaakkee [-AABBPPSSXXeeiikknnqqrrssttvv] [-CC directory] [-DD variable] [-dd flags]
[-EE variable] [-ff makefile] [-II directory] [-jj maxjobs]
[-mm directory] [-VV variable] [-xx warningoptions]
[variable=value] [target ...]
DESCRIPTION
The bbssddmmaakkee utility is a program designed to simplify the maintenance of
other programs. Its input is a list of specifications describing depen-
dency relationships between the generation of files and programs.
First of all, the initial list of specifications will be read from the
system makefile, sys.mk, unless inhibited with the -rr option.
Then the first of BSDmakefile, makefile, and Makefile that can be found
in the current directory, object directory (see .OBJDIR), or search path
(see the -II option) will be read for the main list of dependency specifi-
cations. A different makefile or list of them can be supplied via the -ff
option(s). Finally, if the file .depend can be found in any of the
aforesaid locations, it will also be read (see mkdep(1)).
When bbssddmmaakkee searches for a makefile, its name takes precedence over its
location. For instance, BSDmakefile in the object directory will be
favored over Makefile in the current directory.
The options are as follows:
-AA Make archive errors non-fatal, causing bbssddmmaakkee to just skip the
remainder or all of the archive and continue after printing a
message.
-BB Try to be backwards compatible by executing a single shell per
command and by executing the commands to make the sources of a
dependency line in sequence. This is turned on by default unless
-jj is used.
-CC directory
Change to directory before reading the makefiles or doing any-
thing else. If multiple -CC options are specified, each is inter-
preted relative to the previous one: -CC / -CC etc is equivalent to
-CC /etc.
-DD variable
Define variable to be 1, in the global context.
-dd flags
Turn on debugging, and specify which portions of bbssddmmaakkee are to
print debugging information. Argument flags is one or more of
the following:
A Print all possible debugging information; equivalent to
specifying all of the debugging flags.
a Print debugging information about archive searching and
caching.
c Print debugging information about conditional evaluation.
d Print debugging information about directory searching and
caching.
f Print debugging information about the execution of for
loops.
g1 Print the input graph before making anything.
g2 Print the input graph after making everything, or before
exiting on error.
j Print debugging information about running multiple
shells.
l Print commands in Makefiles regardless of whether or not
they are prefixed by @ or other "quiet" flags. Also
known as "loud" behavior.
m Print debugging information about making targets, includ-
ing modification dates.
s Print debugging information about suffix-transformation
rules.
t Print debugging information about target list mainte-
nance.
v Print debugging information about variable assignment.
-EE variable
Specify a variable whose environment value (if any) will override
macro assignments within makefiles.
-ee Specify that environment values override macro assignments within
makefiles for all variables.
-ff makefile
Specify a makefile to read instead of the default one. If
makefile is not an absolute pathname, bbssddmmaakkee will search for it
as described above. In case makefile is `-', standard input is
read. Multiple -ff options can be supplied, and the makefiles
will be read in that order.
-II directory
Specify a directory in which to search for makefiles and included
makefiles. Multiple -II options can be specified to form a search
path. The system makefile directory (or directories, see the -mm
option) is automatically appended at the tail of this path.
-ii Ignore non-zero exit of shell commands in the makefile. Equiva-
lent to specifying `-' before each command line in the makefile.
-jj maxjobs
Specify the maximum number of jobs that bbssddmmaakkee may have running
at any one time. Turns compatibility mode off, unless the B flag
is also specified.
-kk Continue processing after errors are encountered, but only on
those targets that do not depend on the target whose creation
caused the error.
-mm directory
Specify a directory in which to search for the system makefile
and makefiles included via the <...> style. Multiple -mm options
can be specified to form a search path. This path will override
the default system include path, /usr/share/mk. The system
include path will always be appended to the search path used for
"..."-style inclusions and makefile searches (see the -II option).
-nn Display the commands that would have been executed, but do not
actually execute them.
-PP Collate the output of a given job and display it only when the
job finishes, instead of mixing the output of parallel jobs
together. This option has no effect unless -jj is used too.
-qq Do not execute any commands, but exit 0 if the specified targets
are up-to-date and 1, otherwise.
-rr Do not process the system makefile.
-SS Stop processing when an error is encountered. Default behaviour.
This is needed to negate the -kk option during recursive builds.
-ss Do not echo any commands as they are executed. Equivalent to
specifying `@@' before each command line in the makefile.
-tt Rather than re-building a target as specified in the makefile,
create it or update its modification time to make it appear up-
to-date.
-VV variable
Print bbssddmmaakkee's idea of the value of variable, in the global con-
text. Do not build any targets. Multiple instances of this
option may be specified; the variables will be printed one per
line, with a blank line for each null or undefined variable.
-vv Be extra verbose. For multi-job makes, this will cause file ban-
ners to be generated.
-XX When using the -VV option to print the values of variables, do not
recursively expand the values.
variable=value
Set the value of the variable variable to value.
-xx warningoptions
Specify extended warning options. This option may be specified
several times. A warningoption can be prefixed with ``no'' in
which case the warning is switched off. The currently available
options are:
dirsyntax
Warn if anything except blanks and comments follows an
..eennddiiff or ..eellssee directive.
See also the ..WWAARRNN special target.
There are seven different types of lines in a makefile: file dependency
specifications, shell commands, variable assignments, include statements,
conditional directives, for loops, and comments.
In general, lines may be continued from one line to the next by ending
them with a backslash (`\'). The trailing newline character and initial
whitespace on the following line are compressed into a single space.
FFIILLEE DDEEPPEENNDDEENNCCYY SSPPEECCIIFFIICCAATTIIOONNSS
Dependency lines consist of one or more targets, an operator, and zero or
more sources. This creates a relationship where the targets ``depend''
on the sources and are usually created from them. The exact relationship
between the target and the source is determined by the operator that sep-
arates them. The three operators are as follows:
:: A target is considered out-of-date if its modification time is less
than those of any of its sources. Sources for a target accumulate
over dependency lines when this operator is used. The target is
removed if bbssddmmaakkee is interrupted.
!! Targets are always re-created, but not until all sources have been
examined and re-created as necessary. Sources for a target accumu-
late over dependency lines when this operator is used. The target
is removed if bbssddmmaakkee is interrupted.
:::: If no sources are specified, the target is always re-created. Oth-
erwise, a target is considered out-of-date if any of its sources
has been modified more recently than the target. Sources for a
target do not accumulate over dependency lines when this operator
is used. The target will not be removed if bbssddmmaakkee is interrupted.
Targets and sources may contain the shell wildcard expressions `?', `*',
`[]' and `{}'. The expressions `?', `*' and `[]' may only be used as
part of the final component of the target or source, and must be used to
describe existing files. The expression `{}' need not necessarily be
used to describe existing files. Expansion is in directory order, not
alphabetically as done in the shell.
SSHHEELLLL CCOOMMMMAANNDDSS
Each target may have associated with it a series of shell commands, nor-
mally used to create the target. Each of the commands in this script
must be preceded by a tab. While any target may appear on a dependency
line, only one of these dependencies may be followed by a creation
script, unless the `::::' operator is used.
If the first characters of the command line are `@@', `-', and/or `++', the
command is treated specially. A `@@' causes the command not to be echoed
before it is executed. A `-' causes any non-zero exit status of the com-
mand line to be ignored. A `++' causes the command to be executed even if
-nn is specified on the command line.
VVAARRIIAABBLLEE AASSSSIIGGNNMMEENNTTSS
Variables in bbssddmmaakkee are much like variables in the shell, and, by tradi-
tion, consist of all upper-case letters. The five operators that can be
used to assign values to variables are as follows:
== Assign the value to the variable. Any previous value is overrid-
den.
++== Append the value to the current value of the variable.
??== Assign the value to the variable if it is not already defined.
::== Assign with expansion, i.e., expand the value before assigning it
to the variable. Normally, expansion is not done until the vari-
able is referenced.
!!== Expand the value and pass it to the shell for execution and
assign the result to the variable. Any newlines in the result
are replaced with spaces.
Any whitespace before the assigned value is removed; if the value is
being appended, a single space is inserted between the previous contents
of the variable and the appended value.
Variables are expanded by surrounding the variable name with either curly
braces (`{}') or parentheses (`()') and preceding it with a dollar sign
(`$'). If the variable name contains only a single letter, the surround-
ing braces or parentheses are not required. This shorter form is not
recommended.
Variable substitution occurs at two distinct times, depending on where
the variable is being used. Variables in dependency lines are expanded
as the line is read. Variables in shell commands are expanded when the
shell command is executed.
The four different classes of variables (in order of increasing prece-
dence) are:
Environment variables
Variables defined as part of bbssddmmaakkee's environment.
Global variables
Variables defined in the makefile or in included makefiles.
Command line variables
Variables defined as part of the command line and variables
obtained from the MAKEFLAGS environment variable or the
..MMAAKKEEFFLLAAGGSS target.
Local variables
Variables that are defined specific to a certain target. The
seven local variables are as follows:
.ALLSRC The list of all sources for this target; also known as
`>'.
.ARCHIVE The name of the archive file; also known as `!'.
.IMPSRC The name/path of the source from which the target is to
be transformed (the ``implied'' source); also known as
`<'.
.MEMBER The name of the archive member; also known as `%'.
.OODATE The list of sources for this target that were deemed
out-of-date; also known as `?'.
.PREFIX The file prefix of the file, containing only the file
portion, no suffix or preceding directory components;
also known as `*'.
.TARGET The name of the target; also known as `@'.
The shorter forms `@', `!', `<', `%', `?', `>', and `*' are per-
mitted for backward compatibility and are not recommended. The
six variables `@F', `@D', ` ted for compatibility with AT&T System V UNIX makefiles and are
not recommended.
Four of the local variables may be used in sources on dependency
lines because they expand to the proper value for each target on
the line. These variables are .TARGET, .PREFIX, .ARCHIVE, and
.MEMBER.
In addition, bbssddmmaakkee sets or knows about the following internal variables
or environment variables:
$ A single dollar sign `$', i.e. `$$' expands to a single
dollar sign.
MAKE The name that bbssddmmaakkee was executed with (argv[0]).
.CURDIR A path to the directory where bbssddmmaakkee was executed. The
bbssddmmaakkee utility sets .CURDIR to the canonical path given
by getcwd(3).
.OBJDIR A path to the directory where the targets are built. At
startup, bbssddmmaakkee searches for an alternate directory to
place target files. It will attempt to change into this
special directory and will search this directory for
makefiles not found in the current directory. The fol-
lowing directories are tried in order:
1. ${MAKEOBJDIRPREFIX}/`pwd`
2. ${MAKEOBJDIR}
3. obj.${MACHINE}
4. obj
5. /usr/obj/`pwd`
The first directory that bbssddmmaakkee successfully changes
into is used. If either MAKEOBJDIRPREFIX or MAKEOBJDIR
is set in the environment but bbssddmmaakkee is unable to change
into the corresponding directory, then the current direc-
tory is used without checking the remainder of the list.
If they are undefined and bbssddmmaakkee is unable to change
into any of the remaining three directories, then the
current directory is used. Note, that MAKEOBJDIRPREFIX
and MAKEOBJDIR must be environment variables and should
not be set on bbssddmmaakkee's command line.
The bbssddmmaakkee utility sets .OBJDIR to the canonical path
given by getcwd(3).
.MAKEFILELIST As bbssddmmaakkee reads various makefiles, including the default
files and any obtained from the command line and ..iinncclluuddee
and ..ssiinncclluuddee directives, their names will be automati-
cally appended to the .MAKEFILELIST variable. They are
added right before bbssddmmaakkee begins to parse them, so that
the name of the current makefile is the last word in this
variable.
.MAKEFLAGS The environment variable MAKEFLAGS may contain anything
that may be specified on bbssddmmaakkee's command line. Its
contents are stored in bbssddmmaakkee's .MAKEFLAGS variable.
All options and variable assignments specified on
bbssddmmaakkee's command line are appended to the .MAKEFLAGS
variable which is then entered into the environment as
MAKEFLAGS for all programs which bbssddmmaakkee executes. By
modifying the contents of the .MAKEFLAGS variable, make-
file can alter the contents of the MAKEFLAGS environment
variable made available for all programs which bbssddmmaakkee
executes; compare with the ..MMAAKKEEFFLLAAGGSS special target
below.
When passing macro definitions and flag arguments in the
MAKEFLAGS environment variable, space and tab characters
are quoted by preceding them with a backslash. When
reading the MAKEFLAGS variable from the environment, all
sequences of a backslash and one of space or tab are
replaced just with their second character without causing
a word break. Any other occurrences of a backslash are
retained. Groups of unquoted space, tab and newline
characters cause word breaking.
MFLAGS This variable is provided for backward compatibility and
contains all the options from the MAKEFLAGS environment
variable plus any options specified on bbssddmmaakkee's command
line.
.TARGETS List of targets bbssddmmaakkee is currently building.
.INCLUDES See ..IINNCCLLUUDDEESS special target.
.LIBS See ..LLIIBBSS special target.
MACHINE Name of the machine architecture bbssddmmaakkee is running on,
obtained from the MACHINE environment variable, or
through uname(3) if not defined.
MACHINEARCH Name of the machine architecture bbssddmmaakkee was compiled
for, defined at compilation time.
VPATH Makefiles may assign a colon-delimited list of directo-
ries to VPATH. These directories will be searched for
source files by bbssddmmaakkee after it has finished parsing all
input makefiles.
Variable expansion may be modified to select or modify each word of the
variable (where a ``word'' is whitespace-delimited sequence of charac-
ters). The general format of a variable expansion is as follows:
{variable[:modifier[:...]]}
Each modifier begins with a colon and one of the following special char-
acters. The colon may be escaped with a backslash (`\').
CC/pattern/replacement/[11gg]
Modify each word of the value, substituting every match of
the extended regular expression pattern (see reformat(7))
with the ed(1)-style replacement string. Normally, the first
occurrence of the pattern in each word of the value is
changed. The `1' modifier causes the substitution to apply
to at most one word; the `g' modifier causes the substitution
to apply to as many instances of the search pattern as occur
in the word or words it is found in. Note that `1' and `g'
are orthogonal; the former specifies whether multiple words
are potentially affected, the latter whether multiple substi-
tutions can potentially occur within each affected word.
EE Replaces each word in the variable with its suffix.
HH Replaces each word in the variable with everything but the
last component.
LL Converts variable to lower-case letters.
MMpattern Select only those words that match the rest of the modifier.
The standard shell wildcard characters (`*', `?', and `[]')
may be used. The wildcard characters may be escaped with a
backslash (`\').
NNpattern This is identical to MM, but selects all words which do not
match the rest of the modifier.
OO Order every word in the variable alphabetically.
QQ Quotes every shell meta-character in the variable, so that it
can be passed safely through recursive invocations of
bbssddmmaakkee.
RR Replaces each word in the variable with everything but its
suffix.
SS/oldstring/newstring/[gg]
Modify the first occurrence of oldstring in each word of the
variable's value, replacing it with newstring. If a `g' is
appended to the last slash of the pattern, all occurrences in
each word are replaced. If oldstring begins with a caret
(`^'), oldstring is anchored at the beginning of each word.
If oldstring ends with a dollar sign (`$'), it is anchored
at the end of each word. Inside newstring, an ampersand
(`&') is replaced by oldstring. Any character may be used
as a delimiter for the parts of the modifier string. The
anchoring, ampersand, and delimiter characters may be escaped
with a backslash (`\').
Variable expansion occurs in the normal fashion inside both
oldstring and newstring with the single exception that a
backslash is used to prevent the expansion of a dollar sign
(`$'), not a preceding dollar sign as is usual.
oldstring=newstring
This is the AT&T System V UNIX style variable substitution.
It must be the last modifier specified. If oldstring or
newstring do not contain the pattern matching character %
then it is assumed that they are anchored at the end of each
word, so only suffixes or entire words may be replaced. Oth-
erwise % is the substring of oldstring to be replaced in
newstring
TT Replaces each word in the variable with its last component.
UU Converts variable to upper-case letters.
uu Remove adjacent duplicate words (like uniq(1)).
DDIIRREECCTTIIVVEESS,, CCOONNDDIITTIIOONNAALLSS,, AANNDD FFOORR LLOOOOPPSS
Directives, conditionals, and for loops reminiscent of the C programming
language are provided in bbssddmmaakkee. All such structures are identified by
a line beginning with a single dot (`.') character. The following direc-
tives are supported:
..iinncclluuddee
..iinncclluuddee "file"
Include the specified makefile. Variables between the angle
brackets or double quotes are expanded to form the file name. If
angle brackets are used, the included makefile is expected to be
in the system makefile directory. If double quotes are used, the
including makefile's directory and any directories specified
using the -II option are searched before the system makefile
directory.
..ssiinncclluuddee
..ssiinncclluuddee "file"
Like ..iinncclluuddee, but silently ignored if the file cannot be found
and opened.
..uunnddeeff variable
Un-define the specified global variable. Only global variables
may be un-defined.
..eerrrroorr message
Terminate processing of the makefile immediately. The filename
of the makefile, the line on which the error was encountered and
the specified message are printed to the standard error output
and bbssddmmaakkee terminates with exit code 1. Variables in the mes-
sage are expanded.
..wwaarrnniinngg message
Emit a warning message. The filename of the makefile, the line
on which the warning was encountered, and the specified message
are printed to the standard error output. Variables in the mes-
sage are expanded.
Conditionals are used to determine which parts of the Makefile to
process. They are used similarly to the conditionals supported by the C
pre-processor. The following conditionals are supported:
..iiff [!]expression [operator expression ...]
Test the value of an expression.
..iiffddeeff [!]variable [operator variable ...]
Test the value of a variable.
..iiffnnddeeff [!]variable [operator variable ...]
Test the value of a variable.
..iiffmmaakkee [!]target [operator target ...]
Test the target being built.
..iiffnnmmaakkee [!]target [operator target ...]
Test the target being built.
..eellssee Reverse the sense of the last conditional.
..eelliiff [!]expression [operator expression ...]
A combination of ..eellssee followed by ..iiff.
..eelliiffddeeff [!]variable [operator variable ...]
A combination of ..eellssee followed by ..iiffddeeff.
..eelliiffnnddeeff [!]variable [operator variable ...]
A combination of ..eellssee followed by ..iiffnnddeeff.
..eelliiffmmaakkee [!]target [operator target ...]
A combination of ..eellssee followed by ..iiffmmaakkee.
..eelliiffnnmmaakkee [!]target [operator target ...]
A combination of ..eellssee followed by ..iiffnnmmaakkee.
..eennddiiff End the body of the conditional.
The operator may be any one of the following:
|||| logical OR
&&&& Logical AND; of higher precedence than `||||'.
As in C, bbssddmmaakkee will only evaluate a conditional as far as is necessary
to determine its value. Parentheses may be used to change the order of
evaluation. The boolean operator `!!' may be used to logically negate an
entire conditional. It is of higher precedence than `&&&&'.
The value of expression may be any of the following:
ddeeffiinneedd Takes a variable name as an argument and evaluates to true if
the variable has been defined.
mmaakkee Takes a target name as an argument and evaluates to true if
the target was specified as part of bbssddmmaakkee's command line or
was declared the default target (either implicitly or explic-
itly, see .MAIN) before the line containing the conditional.
eemmppttyy Takes a variable, with possible modifiers, and evaluates to
true if the expansion of the variable would result in an
empty string.
eexxiissttss Takes a file name as an argument and evaluates to true if the
file exists. The file is searched for on the system search
path (see .PATH).
ttaarrggeett Takes a target name as an argument and evaluates to true if
the target has been defined.
An expression may also be an arithmetic or string comparison, with the
left-hand side being a variable expansion. Variable expansion is per-
formed on both sides of the comparison, after which the integral values
are compared. A value is interpreted as hexadecimal if it is preceded by
0x, otherwise it is decimal; octal numbers are not supported. The stan-
dard C relational operators are all supported. If after variable expan-
sion, either the left or right hand side of a `====' or `!!==' operator is
not an integral value, then string comparison is performed between the
expanded variables. If no relational operator is given, it is assumed
that the expanded variable is being compared against 0.
When bbssddmmaakkee is evaluating one of these conditional expressions, and it
encounters a word it does not recognize, either the ``make'' or
``defined'' expression is applied to it, depending on the form of the
conditional. If the form is ..iiff, ..iiffddeeff or ..iiffnnddeeff, the ``defined''
expression is applied. Similarly, if the form is ..iiffmmaakkee or ..iiffnnmmaakkee,
the ``make'' expression is applied.
If the conditional evaluates to true the parsing of the makefile contin-
ues as before. If it evaluates to false, the following lines are
skipped. In both cases this continues until a ..eellssee or ..eennddiiff is found.
For loops are typically used to apply a set of rules to a list of files.
The syntax of a for loop is:
..ffoorr variable iinn expression
..eennddffoorr
After the for expression is evaluated, it is split into words. The iter-
ation variable is successively set to each word, and substituted in the
mmaakkee-rruulleess inside the body of the for loop.
CCOOMMMMEENNTTSS
Comments begin with a hash (`#') character, anywhere but in a shell com-
mand line, and continue to the end of the line.
SSPPEECCIIAALL SSOOUURRCCEESS
..IIGGNNOORREE Ignore any errors from the commands associated with this tar-
get, exactly as if they all were preceded by a dash (`-').
..MMAAKKEE Execute the commands associated with this target even if the
-nn or -tt options were specified. Normally used to mark
recursive bbssddmmaakkee's.
..NNOOTTMMAAIINN Normally bbssddmmaakkee selects the first target it encounters as
the default target to be built if no target was specified.
This source prevents this target from being selected.
..OOPPTTIIOONNAALL If a target is marked with this attribute and bbssddmmaakkee cannot
figure out how to create it, it will ignore this fact and
assume the file is not needed or already exists.
..PPRREECCIIOOUUSS When bbssddmmaakkee is interrupted, it removes any partially made
targets. This source prevents the target from being removed.
..SSIILLEENNTT Do not echo any of the commands associated with this target,
exactly as if they all were preceded by an at sign (`@').
..UUSSEE Turn the target into bbssddmmaakkee's version of a macro. When the
target is used as a source for another target, the other tar-
get acquires the commands, sources, and attributes (except
for ..UUSSEE) of the source. If the target already has commands,
the ..UUSSEE target's commands are appended to them.
..WWAAIITT If special ..WWAAIITT source is appears in a dependency line, the
sources that precede it are made before the sources that suc-
ceed it in the line. Loops are not being detected and tar-
gets that form loops will be silently ignored.
SSPPEECCIIAALL TTAARRGGEETTSS
Special targets may not be included with other targets, i.e., they must
be the only target specified.
..BBEEGGIINN Any command lines attached to this target are executed before
anything else is done.
..DDEEFFAAUULLTT This is sort of a ..UUSSEE rule for any target (that was used
only as a source) that bbssddmmaakkee cannot figure out any other
way to create. Only the shell script is used. The ..IIMMPPSSRRCC
variable of a target that inherits ..DDEEFFAAUULLTT's commands is set
to the target's own name.
..EENNDD Any command lines attached to this target are executed after
everything else is done.
..IIGGNNOORREE Mark each of the sources with the ..IIGGNNOORREE attribute. If no
sources are specified, this is the equivalent of specifying
the -ii option.
..IINNCCLLUUDDEESS A list of suffixes that indicate files that can be included
in a source file. The suffix must have already been declared
with ..SSUUFFFFIIXXEESS; any suffix so declared will have the directo-
ries on its search path (see ..PPAATTHH) placed in the .INCLUDES
special variable, each preceded by a -II flag.
..IINNTTEERRRRUUPPTT If bbssddmmaakkee is interrupted, the commands for this target will
be executed.
..LLIIBBSS This does for libraries what ..IINNCCLLUUDDEESS does for include
files, except that the flag used is -LL.
..MMAAIINN If no target is specified when bbssddmmaakkee is invoked, this tar-
get will be built. This is always set, either explicitly, or
implicitly when bbssddmmaakkee selects the default target, to give
the user a way to refer to the default target on the command
line.
..MMAAKKEEFFLLAAGGSS This target provides a way to specify flags for bbssddmmaakkee when
the makefile is used. The flags are as if typed to the
shell, though the -ff option will have no effect. Flags
(except for -ff) and variable assignments specified as the
source for this target are also appended to the .MAKEFLAGS
internal variable. Please note the difference between this
target and the .MAKEFLAGS internal variable: specifying an
option or variable assignment as the source for this target
will affect both the current makefile and all processes that
bbssddmmaakkee executes.
..MMFFLLAAGGSS Same as above, for backward compatibility.
..NNOOTTPPAARRAALLLLEELL
Disable parallel mode.
..NNOOPPAARRAALLLLEELL
Same as above, for compatibility with other ppmmaakkee variants.
..OORRDDEERR The named targets are made in sequence.
..PPAATTHH The sources are directories which are to be searched for
files not found in the current directory. If no sources are
specified, any previously specified directories are deleted.
Where possible, use of ..PPAATTHH is preferred over use of the
VPATH variable.
..PPAATTHHsuffix
The sources are directories which are to be searched for suf-
fixed files not found in the current directory. The bbssddmmaakkee
utility first searches the suffixed search path, before
reverting to the default path if the file is not found there.
This form is required for ..LLIIBBSS and ..IINNCCLLUUDDEESS to work.
..PPHHOONNYY Apply the ..PPHHOONNYY attribute to any specified sources. Targets
with this attribute are always considered to be out of date.
..PPRREECCIIOOUUSS Apply the ..PPRREECCIIOOUUSS attribute to any specified sources. If
no sources are specified, the ..PPRREECCIIOOUUSS attribute is applied
to every target in the file.
..SSHHEELLLL Select another shell. The sources of this target have the
format key=value. The key is one of:
path Specify the path to the new shell.
name Specify the name of the new shell. This may be
either one of the three builtin shells (see below)
or any other name.
quiet Specify the shell command to turn echoing off.
echo Specify the shell command to turn echoing on.
filter Usually shells print the echo off command before
turning echoing off. This is the exact string
that will be printed by the shell and is used to
filter the shell output to remove the echo off
command.
echoFlag The shell option that turns echoing on.
errFlag The shell option to turn on error checking. If
error checking is on, the shell should exit if a
command returns a non-zero status.
hasErrCtl True if the shell has error control.
check If hasErrCtl is true then this is the shell com-
mand to turn error checking on. If hasErrCtl is
false then this is a command template to echo com-
mands for which error checking is disabled. The
template must contain a `%s'.
ignore If hasErrCtl is true, this is the shell command to
turn error checking off. If hasErrCtl is false,
this is a command template to execute a command so
that errors are ignored. The template must con-
tain a `%s'.
meta This is a string of meta characters of the shell.
builtins This is a string holding all the shell's builtin
commands separated by blanks. The meta and
builtins strings are used in compat mode. When a
command line contains neither a meta character nor
starts with a shell builtin, it is executed
directly without invoking a shell. When one of
these strings (or both) is empty all commands are
executed through a shell.
unsetenv If true, remove the ENV environment variable
before executing any command. This is useful for
the Korn-shell (kksshh).
Values that are strings must be surrounded by double quotes.
Boolean values are specified as `T' or `Y' (in either case)
to mean true. Any other value is taken to mean false.
There are several uses of the ..SSHHEELLLL target:
++oo Selecting one of the builtin shells. This is done by
just specifying the name of the shell with the name key-
word. It is also possible to modify the parameters of
the builtin shell by just specifying other keywords
(except for path).
++oo Using another executable for one of the builtin shells.
This is done by specifying the path to the executable
with the path keyword. If the last component is the same
as the name of the builtin shell, no name needs to be
specified; if it is different, the name must be given:
.SHELL: path="/usr/local/bin/sh"
selects the builtin shell ``sh'' but will execute it from
/usr/local/bin/sh. Like in the previous case, it is pos-
sible to modify parameters of the builtin shell by just
specifying them.
++oo Using an entirely different shell. This is done by spec-
ifying all keywords.
The builtin shells are ``sh'', ``csh'' and ``ksh''. Because
FreeBSD has no kksshh in /bin, it is unwise to specify
name="ksh" without also specifying a path.
..SSIILLEENNTT Apply the ..SSIILLEENNTT attribute to any specified sources. If no
sources are specified, the ..SSIILLEENNTT attribute is applied to
every command in the file.
..SSUUFFFFIIXXEESS Each source specifies a suffix to bbssddmmaakkee. If no sources are
specified, any previous specified suffices are deleted.
..WWAARRNN Each source specifies a warning flag as previously described
for the -xx command line option. Warning flags specified on
the command line take precedence over flags specified in the
makefile. Also, command line warning flags are pushed to
sub-makes through the MAKEFLAGS environment variables so that
a warning flag specified on the command line will influence
all sub-makes. Several flags can be specified on a single
..WWAARRNN target by seperating them with blanks.
ENVIRONMENT The bbssddmmaakkee utility uses the following environment variables, if they
exist: MACHINE, MAKE, MAKEFLAGS, MAKEOBJDIR, and MAKEOBJDIRPREFIX.
FILES .depend list of dependencies
Makefile list of dependencies
makefile list of dependencies
obj object directory
sys.mk system makefile
/usr/share/mk default system makefile directory
/usr/obj default MAKEOBJDIRPREFIX directory.
EEXXAAMMPPLLEESS
List all included makefiles in order visited:
make -V .MAKEFILELIST | tr \ \\n
CCOOMMPPAATTIIBBIILLIITTYY
Older versions of bbssddmmaakkee used MAKE instead of MAKEFLAGS. This was
removed for POSIX compatibility. The internal variable MAKE is set to
the same value as .MAKE; support for this may be removed in the future.
Most of the more esoteric features of bbssddmmaakkee should probably be avoided
for greater compatibility.
SEE ALSO
mkdep(1),
HISTORY A bbssddmmaakkee command appeared in PWB UNIX.
BUGS
The determination of .OBJDIR is contorted to the point of absurdity.
In the presence of several ..MMAAIINN special targets, bbssddmmaakkee silently
ignores all but the first.
.TARGETS is not set to the default target when bbssddmmaakkee is invoked without
a target name and no ..MMAAIINN special target exists.
The evaluation of expression in a test is very simple-minded. Currently,
the only form that works is `.if ${VAR} op something' For instance, you
should write tests as `.if ${VAR} == string' not the other way around,
which would give you an error.
For loops are expanded before tests, so a fragment such as:
.for ARCH in ${SHAREDARCHS}
.if ${ARCH} == ${MACHINE}
...
.endif
.endfor
will not work, and should be rewritten as:
.for ARCH in ${SHAREDARCHS}
.if ${MACHINE} == ${ARCH}
...
.endif
.endfor
The parsing code is broken with respect to handling a semicolon after a
colon, so a fragment like this will fail:
HDRS= foo.h bar.h
all:
.for h in ${HDRS:S;^;${.CURDIR}/;}
...
.endfor
A trailing backslash in a variable value defined on the command line
causes the delimiting space in the MAKEFLAGS environment variable to be
preceeded by that backslash. That causes a submake to not treat that
space as a word delimiter. Fixing this requires a larger rewrite of the
code handling command line macros and assignments to .MAKEFLAGS.
BSD October 14, 2005 BSD