1994-05-30 19:09:18 +00:00
|
|
|
# @(#)bsd.README 8.2 (Berkeley) 4/2/94
|
|
|
|
|
2003-05-17 18:03:05 +00:00
|
|
|
This is the README file for the "include" files for the FreeBSD
|
|
|
|
source tree. The files are installed in /usr/share/mk, and are by
|
|
|
|
convention, named with the suffix ".mk". These files store several
|
|
|
|
build options and should be handled with caution.
|
1994-10-09 21:22:32 +00:00
|
|
|
|
2003-05-17 18:03:05 +00:00
|
|
|
Note, this file is not intended to replace reading through the .mk
|
|
|
|
files for anything tricky.
|
|
|
|
|
|
|
|
There are two main types of make include files. One type is the generally
|
|
|
|
usable make include files, such as bsd.prog.mk and bsd.lib.mk. The other is
|
|
|
|
the internal make include files, such as bsd.files.mk and bsd.man.mk, which
|
|
|
|
can not/should not be used directly but are used by the other make include
|
|
|
|
files. In most cases it is only interesting to include bsd.prog.mk or
|
|
|
|
bsd.lib.mk.
|
1997-03-09 02:23:40 +00:00
|
|
|
|
2015-08-21 16:05:56 +00:00
|
|
|
bsd.arch.inc.mk - includes arch-specific Makefile.$arch
|
2019-10-15 21:27:06 +00:00
|
|
|
bsd.compat.mk - definitions for building programs against compat ABIs
|
2015-08-21 19:51:27 +00:00
|
|
|
bsd.compiler.mk - defined based on current compiler
|
2015-10-09 21:57:42 +00:00
|
|
|
bsd.confs.mk - install of configuration files
|
2015-08-21 19:51:19 +00:00
|
|
|
bsd.cpu.mk - sets CPU/arch-related variables (included from sys.mk)
|
2015-10-24 05:00:20 +00:00
|
|
|
bsd.crunchgen.mk - building crunched binaries using crunchgen(1)
|
1997-03-09 02:23:40 +00:00
|
|
|
bsd.dep.mk - handle Makefile dependencies
|
2018-07-23 16:11:03 +00:00
|
|
|
bsd.dirs.mk - handle directory creation
|
1997-03-09 02:23:40 +00:00
|
|
|
bsd.doc.mk - building troff system documents
|
2015-08-27 22:42:02 +00:00
|
|
|
bsd.endian.mk - TARGET_ENDIAN=1234(little) or 4321 (big) for target
|
2003-05-17 18:03:05 +00:00
|
|
|
bsd.files.mk - install of general purpose files
|
|
|
|
bsd.incs.mk - install of include files
|
2015-08-21 17:45:18 +00:00
|
|
|
bsd.info.mk - building GNU Info hypertext system (deprecated)
|
2003-05-17 18:03:05 +00:00
|
|
|
bsd.init.mk - initialization for the make include files
|
1997-03-09 02:23:40 +00:00
|
|
|
bsd.kmod.mk - building loadable kernel modules
|
|
|
|
bsd.lib.mk - support for building libraries
|
|
|
|
bsd.libnames.mk - define library names
|
2003-05-17 18:03:05 +00:00
|
|
|
bsd.links.mk - install of links (sym/hard)
|
|
|
|
bsd.man.mk - install of manual pages and their links
|
|
|
|
bsd.nls.mk - build and install of NLS catalogs
|
1997-03-09 02:23:40 +00:00
|
|
|
bsd.obj.mk - creating 'obj' directories and cleaning up
|
|
|
|
bsd.own.mk - define common variables
|
|
|
|
bsd.port.mk - building ports
|
2003-05-17 18:03:05 +00:00
|
|
|
bsd.port.post.mk - building ports
|
|
|
|
bsd.port.pre.mk - building ports
|
1997-03-09 02:23:40 +00:00
|
|
|
bsd.port.subdir.mk - targets for building subdirectories for ports
|
|
|
|
bsd.prog.mk - building programs from source files
|
2015-09-25 16:27:11 +00:00
|
|
|
bsd.progs.mk - build multiple programs from sources
|
2005-11-10 10:03:22 +00:00
|
|
|
bsd.snmpmod.mk - building modules for the SNMP daemon bsnmpd
|
1997-03-09 02:23:40 +00:00
|
|
|
bsd.subdir.mk - targets for building subdirectories
|
2003-05-17 18:03:05 +00:00
|
|
|
bsd.sys.mk - common settings used for building FreeBSD sources
|
2014-03-15 09:27:59 +00:00
|
|
|
bsd.test.mk - building test programs from source files
|
2003-05-17 18:03:05 +00:00
|
|
|
sys.mk - default rules for all makes
|
1997-03-09 02:23:40 +00:00
|
|
|
|
2003-05-17 18:03:05 +00:00
|
|
|
This file does not document bsd.port*.mk. They are documented in ports(7).
|
1994-05-30 19:09:18 +00:00
|
|
|
|
2003-05-17 18:03:05 +00:00
|
|
|
See also make(1), mkdep(1), style.Makefile(5) and `PMake - A
|
|
|
|
Tutorial', located in /usr/share/doc/psd/12.make.
|
|
|
|
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|
|
|
|
|
|
|
|
Random things worth knowing about this document:
|
|
|
|
|
|
|
|
If appropriate when documenting the variables the default value is
|
|
|
|
indicated using square brackets e.g. [gzip].
|
|
|
|
In some cases the default value depend on other values (e.g. system
|
|
|
|
architecture). In these cases the most common value is indicated.
|
1994-05-30 19:09:18 +00:00
|
|
|
|
2003-05-17 18:03:05 +00:00
|
|
|
This document contains some simple examples of the usage of the BSD make
|
|
|
|
include files. For more examples look at the makefiles in the FreeBSD
|
|
|
|
source tree.
|
1997-03-09 15:51:07 +00:00
|
|
|
|
1994-05-30 19:09:18 +00:00
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|
|
|
|
|
|
|
|
RANDOM THINGS WORTH KNOWING:
|
|
|
|
|
2003-05-17 18:03:05 +00:00
|
|
|
The files are like C-style #include files, and pretty much behave like
|
1994-05-30 19:09:18 +00:00
|
|
|
you'd expect. The syntax is slightly different in that a single '.' is
|
|
|
|
used instead of the hash mark, i.e. ".include <bsd.prog.mk>".
|
|
|
|
|
|
|
|
One difference that will save you lots of debugging time is that inclusion
|
|
|
|
of the file is normally done at the *end* of the Makefile. The reason for
|
|
|
|
this is because .mk files often modify variables and behavior based on the
|
|
|
|
values of variables set in the Makefile. To make this work, remember that
|
|
|
|
the FIRST target found is the target that is used, i.e. if the Makefile has:
|
|
|
|
|
|
|
|
a:
|
|
|
|
echo a
|
|
|
|
a:
|
|
|
|
echo a number two
|
|
|
|
|
|
|
|
the command "make a" will echo "a". To make things confusing, the SECOND
|
|
|
|
variable assignment is the overriding one, i.e. if the Makefile has:
|
|
|
|
|
|
|
|
a= foo
|
|
|
|
a= bar
|
|
|
|
|
|
|
|
b:
|
|
|
|
echo ${a}
|
|
|
|
|
|
|
|
the command "make b" will echo "bar". This is for compatibility with the
|
|
|
|
way the V7 make behaved.
|
|
|
|
|
|
|
|
It's fairly difficult to make the BSD .mk files work when you're building
|
2010-05-22 20:19:12 +00:00
|
|
|
multiple programs in a single directory. It's a lot easier to split up
|
|
|
|
the programs than to deal with the problem. Most of the agony comes from
|
|
|
|
making the "obj" directory stuff work right, not because we switch to a new
|
|
|
|
version of make. So, don't get mad at us, figure out a better way to handle
|
|
|
|
multiple architectures so we can quit using the symbolic link stuff.
|
2010-05-22 16:30:33 +00:00
|
|
|
(Imake doesn't count.)
|
1994-05-30 19:09:18 +00:00
|
|
|
|
|
|
|
The file .depend in the source directory is expected to contain dependencies
|
|
|
|
for the source files. This file is read automatically by make after reading
|
|
|
|
the Makefile.
|
|
|
|
|
|
|
|
The variable DESTDIR works as before. It's not set anywhere but will change
|
|
|
|
the tree where the file gets installed.
|
|
|
|
|
|
|
|
The profiled libraries are no longer built in a different directory than
|
|
|
|
the regular libraries. A new suffix, ".po", is used to denote a profiled
|
2016-09-25 16:50:31 +00:00
|
|
|
object, and ".pico" denotes a position-independent relocatable object.
|
2018-05-09 10:28:24 +00:00
|
|
|
".nossppico" denotes a position-independent relocatable object without
|
2021-08-02 08:48:21 +00:00
|
|
|
stack smashing protection and without sanitizer instrumentation.
|
1994-05-30 19:09:18 +00:00
|
|
|
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|
|
|
|
|
2015-08-21 19:51:19 +00:00
|
|
|
The following variables are common:
|
|
|
|
|
2016-06-22 20:31:49 +00:00
|
|
|
AFLAGS.${SRC}
|
|
|
|
Flags dependent on source file name.
|
2019-06-15 17:08:24 +00:00
|
|
|
AFLAGS.${TARGET}
|
|
|
|
Flags dependent on output file name.
|
2016-03-26 03:46:12 +00:00
|
|
|
ACFLAGS.${SRC}
|
|
|
|
Flags dependent on source file name.
|
2019-06-15 17:08:24 +00:00
|
|
|
ACFLAGS.${TARGET}
|
|
|
|
Flags dependent on output file name.
|
2016-03-26 03:46:12 +00:00
|
|
|
CFLAGS.${SRC}
|
|
|
|
Flags dependent on source file name.
|
2019-06-15 17:08:24 +00:00
|
|
|
CFLAGS.${TARGET}
|
|
|
|
Flags dependent on output file name.
|
2015-08-21 19:51:27 +00:00
|
|
|
CFLAGS.${COMPILER_TYPE}
|
2017-03-08 05:49:58 +00:00
|
|
|
Flags dependent on compiler added to CFLAGS.
|
2015-08-21 19:51:27 +00:00
|
|
|
CFLAGS.${MACHINE_ARCH}
|
|
|
|
Architectural flags added to CFLAGS.
|
2015-08-21 19:51:19 +00:00
|
|
|
CFLAGS_NO_SIMD Add this to CFLAGS for programs that don't want any SIMD
|
|
|
|
instructions generated. It is setup in bsd.cpu.mk to an
|
|
|
|
appropriate value for the compiler and target.
|
2015-08-21 19:51:27 +00:00
|
|
|
CXXFLAGS.${COMPILER_TYPE}
|
|
|
|
Flags dependent on compiler added to CXXFLAGS.
|
|
|
|
CXXFLAGS.${MACHINE_ARCH}
|
|
|
|
Architectural flags added to CXXFLAGS.
|
2016-03-26 03:46:12 +00:00
|
|
|
CXXFLAGS.${SRC}
|
|
|
|
Flags dependent on source file name.
|
2019-06-15 17:08:24 +00:00
|
|
|
CXXFLAGS.${TARGET}
|
|
|
|
Flags dependent on output file name.
|
2015-08-21 19:51:27 +00:00
|
|
|
COMPILER_FEATURES
|
|
|
|
A list of features that the compiler supports. Zero or
|
|
|
|
more of:
|
|
|
|
c++11 Supports full C++ 11 standard.
|
|
|
|
|
|
|
|
COMPILER_TYPE Type of compiler, either clang or gcc, though other
|
|
|
|
values are possible. Don't assume != clang == gcc.
|
|
|
|
|
|
|
|
COMPILER_VERSION
|
|
|
|
A numeric constant equal to:
|
|
|
|
major * 10000 + minor * 100 + tiny
|
|
|
|
for the compiler's self-reported version.
|
2015-08-21 19:51:19 +00:00
|
|
|
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|
|
|
|
|
1994-05-30 19:09:18 +00:00
|
|
|
The include file <sys.mk> has the default rules for all makes, in the BSD
|
|
|
|
environment or otherwise. You probably don't want to touch this file.
|
|
|
|
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|
|
|
|
|
2015-08-21 16:05:56 +00:00
|
|
|
The include file <bsd.arch.inc.mk> includes other Makefiles for specific
|
|
|
|
architectures, if they exist. It will include the first of the following
|
|
|
|
files that it finds: Makefile.${MACHINE}, Makefile.${MACHINE_ARCH},
|
|
|
|
Makefile.${MACHINE_CPUARCH}
|
|
|
|
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|
|
|
|
|
1994-05-30 19:09:18 +00:00
|
|
|
The include file <bsd.man.mk> handles installing manual pages and their
|
|
|
|
links.
|
|
|
|
|
2001-09-05 11:24:34 +00:00
|
|
|
It has three targets:
|
1994-05-30 19:09:18 +00:00
|
|
|
|
2001-09-05 11:24:34 +00:00
|
|
|
all-man:
|
|
|
|
build manual pages.
|
1994-05-30 19:09:18 +00:00
|
|
|
maninstall:
|
2001-09-05 11:24:34 +00:00
|
|
|
install the manual pages and their links.
|
|
|
|
manlint:
|
|
|
|
verify the validity of manual pages.
|
1994-05-30 19:09:18 +00:00
|
|
|
|
|
|
|
It sets/uses the following variables:
|
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
MAN The manual pages to be installed (use a .1 - .9 suffix).
|
|
|
|
|
1994-05-30 19:09:18 +00:00
|
|
|
MANDIR Base path for manual installation.
|
|
|
|
|
|
|
|
MANGRP Manual group.
|
|
|
|
|
|
|
|
MANMODE Manual mode.
|
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
MANOWN Manual owner.
|
|
|
|
|
1994-05-30 19:09:18 +00:00
|
|
|
MANSUBDIR Subdirectory under the manual page section, i.e. "/vax"
|
|
|
|
or "/tahoe" for machine specific manual pages.
|
|
|
|
|
2000-03-23 16:48:04 +00:00
|
|
|
MLINKS List of manual page links (using a .1 - .9 suffix). The
|
1994-05-30 19:09:18 +00:00
|
|
|
linked-to file must come first, the linked file second,
|
2014-11-21 17:55:38 +00:00
|
|
|
and there may be multiple pairs. The files are hard-linked.
|
1994-05-30 19:09:18 +00:00
|
|
|
|
2001-03-28 15:12:29 +00:00
|
|
|
The include file <bsd.man.mk> includes a file named "../Makefile.inc" if
|
|
|
|
it exists.
|
1994-05-30 19:09:18 +00:00
|
|
|
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|
|
|
|
|
|
|
|
The include file <bsd.own.mk> contains the owners, groups, etc. for both
|
|
|
|
manual pages and binaries.
|
|
|
|
|
|
|
|
It has no targets.
|
|
|
|
|
|
|
|
It sets/uses the following variables:
|
|
|
|
|
|
|
|
BINGRP Binary group.
|
|
|
|
|
|
|
|
BINMODE Binary mode.
|
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
BINOWN Binary owner.
|
|
|
|
|
1994-05-30 19:09:18 +00:00
|
|
|
MANDIR Base path for manual installation.
|
|
|
|
|
|
|
|
MANGRP Manual group.
|
|
|
|
|
|
|
|
MANMODE Manual mode.
|
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
MANOWN Manual owner.
|
|
|
|
|
2018-06-29 16:07:56 +00:00
|
|
|
INSTALL_LINK Command to install a hard link.
|
|
|
|
|
|
|
|
INSTALL_SYMLINK Command to install a symbolic link.
|
|
|
|
|
|
|
|
INSTALL_RSYMLINK Command to install a relative symbolic link.
|
|
|
|
|
|
|
|
LINKOWN Owner of hard links created by INSTALL_LINK.
|
|
|
|
|
|
|
|
LINKGRP Group of hard links created by INSTALL_LINK.
|
|
|
|
|
|
|
|
LINKMODE Mode of hard links created by INSTALL_LINK.
|
|
|
|
|
|
|
|
SYMLINKOWN Owner of hard links created by INSTALL_[R]SYMLINK.
|
|
|
|
|
|
|
|
SYMLINKGRP Group of hard links created by INSTALL_[R]SYMLINK.
|
|
|
|
|
|
|
|
SYMLINKMODE Mode of hard links created by INSTALL_[R]SYMLINK.
|
|
|
|
|
1994-05-30 19:09:18 +00:00
|
|
|
This file is generally useful when building your own Makefiles so that
|
|
|
|
they use the same default owners etc. as the rest of the tree.
|
|
|
|
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|
|
|
|
|
|
|
|
The include file <bsd.prog.mk> handles building programs from one or
|
|
|
|
more source files, along with their manual pages. It has a limited number
|
|
|
|
of suffixes, consistent with the current needs of the BSD tree.
|
|
|
|
|
|
|
|
It has seven targets:
|
|
|
|
|
|
|
|
all:
|
|
|
|
build the program and its manual page
|
|
|
|
clean:
|
2006-06-18 11:26:17 +00:00
|
|
|
remove the program and any object files.
|
1994-05-30 19:09:18 +00:00
|
|
|
cleandir:
|
|
|
|
remove all of the files removed by the target clean, as
|
|
|
|
well as .depend, tags, and any manual pages.
|
|
|
|
depend:
|
|
|
|
make the dependencies for the source files, and store
|
|
|
|
them in the file .depend.
|
|
|
|
install:
|
|
|
|
install the program and its manual pages; if the Makefile
|
|
|
|
does not itself define the target install, the targets
|
|
|
|
beforeinstall and afterinstall may also be used to cause
|
|
|
|
actions immediately before and after the install target
|
|
|
|
is executed.
|
|
|
|
tags:
|
|
|
|
create a tags file for the source files.
|
|
|
|
|
|
|
|
It sets/uses the following variables:
|
|
|
|
|
2016-06-22 20:31:49 +00:00
|
|
|
ACFLAGS Flags to the compiler when preprocessing and
|
|
|
|
assembling .S files.
|
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
AFLAGS Flags to the assembler when assembling .s files.
|
1994-05-30 19:09:18 +00:00
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
BINGRP Binary group.
|
1994-05-30 19:09:18 +00:00
|
|
|
|
|
|
|
BINMODE Binary mode.
|
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
BINOWN Binary owner.
|
1994-05-30 19:09:18 +00:00
|
|
|
|
2004-08-13 14:30:26 +00:00
|
|
|
CFLAGS Flags to the compiler when creating C objects.
|
1994-05-30 19:09:18 +00:00
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
CLEANDIRS Additional files (CLEANFILES) and directories (CLEANDIRS) to
|
|
|
|
CLEANFILES remove during clean and cleandir targets. "rm -rf" and
|
|
|
|
"rm -f" are used, respectively.
|
|
|
|
|
2018-07-23 16:11:03 +00:00
|
|
|
DIRS A list of variables referring to directories. For example:
|
|
|
|
|
|
|
|
DIRS+= FOO
|
|
|
|
FOO= /usr/share/foo
|
|
|
|
|
|
|
|
Owner, Group, Mode and Flags are handled by FOO_OWN,
|
|
|
|
FOO_GRP, FOO_MODE and FOO_FLAGS, respectively.
|
|
|
|
|
|
|
|
This allows FILESDIR to be set to FOO, and the directory
|
|
|
|
will be created before the files are installed and the
|
|
|
|
dependencies will be set correctly.
|
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
DPADD Additional dependencies for the program. Usually used for
|
|
|
|
libraries. For example, to depend on the compatibility and
|
|
|
|
utility libraries use:
|
|
|
|
|
|
|
|
DPADD=${LIBCOMPAT} ${LIBUTIL}
|
|
|
|
|
|
|
|
There is a predefined identifier for each (non-profiled,
|
|
|
|
non-shared) library and object. Library file names are
|
|
|
|
transformed to identifiers by removing the extension and
|
|
|
|
converting to upper case.
|
|
|
|
|
|
|
|
There are no special identifiers for profiled or shared
|
|
|
|
libraries or objects. The identifiers for the standard
|
|
|
|
libraries are used in DPADD. This works correctly iff all
|
|
|
|
the libraries are built at the same time. Unfortunately,
|
|
|
|
it causes unnecessary relinks to shared libraries when
|
|
|
|
only the static libraries have changed. Dependencies on
|
|
|
|
shared libraries should be only on the library version
|
|
|
|
numbers.
|
|
|
|
|
2001-12-17 13:59:35 +00:00
|
|
|
FILES A list of non-executable files.
|
|
|
|
The installation is controlled by the FILESNAME, FILESOWN,
|
|
|
|
FILESGRP, FILESMODE, FILESDIR variables that can be
|
|
|
|
further specialized by FILES<VAR>_<file>.
|
|
|
|
|
1994-05-30 19:09:18 +00:00
|
|
|
LDADD Additional loader objects. Usually used for libraries.
|
|
|
|
For example, to load with the compatibility and utility
|
|
|
|
libraries, use:
|
|
|
|
|
2012-05-24 20:00:58 +00:00
|
|
|
LDADD=-lutil -lcompat
|
1994-05-30 19:09:18 +00:00
|
|
|
|
2022-02-20 16:26:04 +00:00
|
|
|
LDADD.${TARGET}
|
2019-06-15 17:08:24 +00:00
|
|
|
Loader objects dependent on output file name.
|
|
|
|
|
2014-07-25 21:10:30 +00:00
|
|
|
LDFLAGS Additional loader flags. Passed to the loader via CC,
|
|
|
|
since that's used to link programs as well, so loader
|
|
|
|
specific flags need to be prefixed with -Wl, to work.
|
1994-05-30 19:09:18 +00:00
|
|
|
|
2019-06-15 17:08:24 +00:00
|
|
|
LDFLAGS.${TARGET}
|
|
|
|
Flags dependent on output file name.
|
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
LIBADD Additional libraries. This is for base system libraries
|
|
|
|
and is only valid inside of the /usr/src tree.
|
2017-03-08 05:49:58 +00:00
|
|
|
Use LIBADD=name instead of LDADD=-lname.
|
2017-03-07 17:38:52 +00:00
|
|
|
|
2019-06-15 17:08:24 +00:00
|
|
|
LIBADD.${TARGET}
|
|
|
|
Libraries dependent on output file name.
|
|
|
|
|
1994-05-30 19:09:18 +00:00
|
|
|
LINKS The list of binary links; should be full pathnames, the
|
|
|
|
linked-to file coming first, followed by the linked
|
|
|
|
file. The files are hard-linked. For example, to link
|
|
|
|
/bin/test and /bin/[, use:
|
|
|
|
|
2017-03-07 17:42:23 +00:00
|
|
|
LINKS= /bin/test /bin/[
|
1994-05-30 19:09:18 +00:00
|
|
|
|
2018-06-29 16:07:56 +00:00
|
|
|
LINKOWN Owner of links created with LINKS [${BINOWN}].
|
|
|
|
|
|
|
|
LINKGRP Group of links created with LINKS [${BINGRP}].
|
|
|
|
|
|
|
|
LINKMODE Mode of links created with LINKS [${BINMODE}].
|
|
|
|
|
|
|
|
|
2017-03-07 17:53:53 +00:00
|
|
|
MAN Manual pages. If no MAN variable is defined,
|
|
|
|
"MAN=${PROG}.1" is assumed. See bsd.man.mk for more details.
|
1994-05-30 19:09:18 +00:00
|
|
|
|
|
|
|
PROG The name of the program to build. If not supplied, nothing
|
|
|
|
is built.
|
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
PROGNAME The name that the above program will be installed as, if
|
|
|
|
different from ${PROG}.
|
|
|
|
|
2002-04-11 10:44:30 +00:00
|
|
|
PROG_CXX If defined, the name of the program to build. Also
|
|
|
|
causes <bsd.prog.mk> to link the program with the
|
|
|
|
standard C++ library. PROG_CXX overrides the value
|
|
|
|
of PROG if PROG is also set.
|
|
|
|
|
2015-09-24 00:17:00 +00:00
|
|
|
PROGS When used with <bsd.progs.mk>, allow building multiple
|
2017-03-08 05:49:58 +00:00
|
|
|
PROGS_CXX PROG and PROG_CXX in one Makefile. To define
|
2015-09-24 00:17:00 +00:00
|
|
|
individual variables for each program the VAR.prog
|
|
|
|
syntax should be used. For example:
|
|
|
|
|
|
|
|
PROGS= foo bar
|
|
|
|
SRCS.foo= foo_src.c
|
2015-09-24 00:22:48 +00:00
|
|
|
LDADD.foo= -lutil
|
2015-09-24 00:17:00 +00:00
|
|
|
SRCS.bar= bar_src.c
|
|
|
|
|
2016-04-14 22:32:56 +00:00
|
|
|
The supported variables are:
|
|
|
|
- BINDIR
|
|
|
|
- BINGRP
|
|
|
|
- BINMODE
|
|
|
|
- BINOWN
|
|
|
|
- CFLAGS
|
|
|
|
- CXXFLAGS
|
|
|
|
- DEBUG_FLAGS
|
|
|
|
- DPADD
|
|
|
|
- DPSRCS
|
2016-08-11 17:06:48 +00:00
|
|
|
- INTERNALPROG (no installation)
|
2016-04-14 22:32:56 +00:00
|
|
|
- LDADD
|
|
|
|
- LDFLAGS
|
|
|
|
- LIBADD
|
|
|
|
- LINKS
|
|
|
|
- MAN
|
|
|
|
- MLINKS
|
2021-01-06 17:55:06 +00:00
|
|
|
- MK_WERROR=no
|
2016-04-14 22:32:56 +00:00
|
|
|
- PROGNAME
|
|
|
|
- SRCS
|
|
|
|
- STRIP
|
|
|
|
- WARNS
|
2015-09-24 00:17:00 +00:00
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
SCRIPTS A list of interpreter scripts [file.{sh,csh,pl,awk,...}].
|
|
|
|
The installation is controlled by the SCRIPTSNAME, SCRIPTSOWN,
|
|
|
|
SCRIPTSGRP, SCRIPTSMODE, SCRIPTSDIR variables that can be
|
|
|
|
further specialized by SCRIPTS<VAR>_<script>.
|
2001-04-02 11:44:20 +00:00
|
|
|
|
1999-11-30 20:24:44 +00:00
|
|
|
SRCS List of source files to build the program. If SRCS is not
|
2002-04-11 10:44:30 +00:00
|
|
|
defined, it's assumed to be ${PROG}.c or, if PROG_CXX is
|
|
|
|
defined, ${PROG_CXX}.cc.
|
1994-05-30 19:09:18 +00:00
|
|
|
|
|
|
|
STRIP The flag passed to the install program to cause the binary
|
2004-02-05 20:16:18 +00:00
|
|
|
to be stripped. This is to be used when building your
|
|
|
|
own install script so that the entire system can be made
|
|
|
|
stripped/not-stripped using a single nob.
|
1994-05-30 19:09:18 +00:00
|
|
|
|
|
|
|
SUBDIR A list of subdirectories that should be built as well.
|
|
|
|
Each of the targets will execute the same target in the
|
|
|
|
subdirectories.
|
|
|
|
|
2001-03-28 15:12:29 +00:00
|
|
|
The include file <bsd.prog.mk> includes the file named "../Makefile.inc"
|
|
|
|
if it exists, as well as the include file <bsd.man.mk>.
|
1994-05-30 19:09:18 +00:00
|
|
|
|
|
|
|
Some simple examples:
|
|
|
|
|
|
|
|
To build foo from foo.c with a manual page foo.1, use:
|
|
|
|
|
|
|
|
PROG= foo
|
|
|
|
|
|
|
|
.include <bsd.prog.mk>
|
|
|
|
|
|
|
|
To build foo from foo.c with a manual page foo.2, add the line:
|
|
|
|
|
2006-03-15 15:49:38 +00:00
|
|
|
MAN= foo.2
|
1994-05-30 19:09:18 +00:00
|
|
|
|
|
|
|
If foo does not have a manual page at all, add the line:
|
|
|
|
|
2014-04-13 05:21:56 +00:00
|
|
|
MAN=
|
1994-05-30 19:09:18 +00:00
|
|
|
|
|
|
|
If foo has multiple source files, add the line:
|
|
|
|
|
|
|
|
SRCS= a.c b.c c.c d.c
|
|
|
|
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|
|
|
|
|
2019-10-31 20:37:19 +00:00
|
|
|
The include file, <bsd.compat.mk>, allows programs (built with
|
|
|
|
<bsd.prog.mk>) to be built for one the ABI(s) supported by the
|
|
|
|
top-level Makefile.libcompat. It requires that <bsd.prog.mk> also be
|
|
|
|
included.
|
|
|
|
|
|
|
|
NEED_COMPAT Build and link targeting a compatibility ABI or fail if it
|
|
|
|
is not available. Supported values are "32", "soft", and
|
|
|
|
"any" being a wildcard.
|
|
|
|
|
|
|
|
WANT_COMPAT Similar to NEED_COMPAT, but build with the base ABI if
|
|
|
|
the specified ABI is not available.
|
|
|
|
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|
|
|
|
|
2017-01-09 04:35:55 +00:00
|
|
|
The include file, <bsd.snmpmod.mk>, handles building MIB modules for bsnmpd
|
|
|
|
from one or more source files, along with their manual pages. It has a
|
|
|
|
limited number of suffixes, consistent with the current needs of the BSD
|
|
|
|
tree.
|
|
|
|
|
|
|
|
bsd.snmpmod.mk leverages bsd.lib.mk for building MIB modules and
|
|
|
|
bsd.files.mk for installing MIB description and definition files.
|
|
|
|
|
2017-01-17 03:38:49 +00:00
|
|
|
It implements the following additional targets:
|
|
|
|
|
|
|
|
smilint:
|
|
|
|
execute smilint on the MIBs defined by BMIBS.
|
|
|
|
|
|
|
|
The net-mgmt/libsmi package must be installed before
|
|
|
|
executing this target. The net-mgmt/net-snmp package
|
|
|
|
should be installed as well to reduce false positives
|
|
|
|
from smilint.
|
2017-01-09 04:35:55 +00:00
|
|
|
|
|
|
|
It sets/uses the following variables:
|
|
|
|
|
|
|
|
BMIBS The MIB definitions to install.
|
|
|
|
|
|
|
|
BMIBSDIR The directory where the MIB definitions are installed.
|
|
|
|
This defaults to `${SHAREDIR}/snmp/mibs`.
|
|
|
|
|
|
|
|
DEFS The MIB description files to install.
|
|
|
|
|
|
|
|
DEFSDIR The directory where MIB description files are installed.
|
|
|
|
This defaults to `${SHAREDIR}/snmp/defs`.
|
|
|
|
|
|
|
|
EXTRAMIBDEFS Extra MIB description files to use as input when
|
|
|
|
generating ${MOD}_oid.h and ${MOD}_tree.[ch].
|
|
|
|
|
|
|
|
EXTRAMIBSYMS Extra MIB definition files used only for extracting
|
|
|
|
symbols.
|
|
|
|
|
|
|
|
EXTRAMIBSYMS are useful when resolving inter-module
|
|
|
|
dependencies and are useful with files containing only
|
|
|
|
enum-definitions.
|
|
|
|
|
|
|
|
See ${MOD}_oid.h for more details.
|
|
|
|
|
2017-01-17 03:38:49 +00:00
|
|
|
LOCALBASE The package root where smilint and the net-snmp
|
|
|
|
definitions can be found
|
|
|
|
|
2017-01-09 04:35:55 +00:00
|
|
|
MOD The bsnmpd module name.
|
|
|
|
|
2017-01-17 03:38:49 +00:00
|
|
|
SMILINT smilint binary to use with the smilint make target.
|
|
|
|
|
|
|
|
SMILINT_FLAGS flags to pass to smilint.
|
|
|
|
|
|
|
|
SMIPATH A colon-separated directory path where MIBs definitions
|
|
|
|
can be found. See "SMIPATH" in smi_config for more
|
|
|
|
details.
|
|
|
|
|
2017-01-09 04:35:55 +00:00
|
|
|
XSYM MIB names to extract symbols for. See ${MOD}_oid.h for
|
|
|
|
more details.
|
|
|
|
|
|
|
|
It generates the following files:
|
|
|
|
|
|
|
|
${MOD}_tree.c A source file and header which programmatically describes
|
|
|
|
${MOD}_tree.h the MIB (type, OID name, ACCESS attributes, etc).
|
|
|
|
|
|
|
|
The files are generated via "gensnmptree -p".
|
|
|
|
|
|
|
|
See gensnmptree(1) for more details.
|
|
|
|
|
|
|
|
${MOD}_oid.h A header which programmatically describes the MIB root and
|
|
|
|
MIB tables.
|
|
|
|
|
|
|
|
The files are generated via "gensnmptree -e".
|
|
|
|
|
|
|
|
See gensnmptree(1) for more details.
|
|
|
|
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|
|
|
|
|
1994-05-30 19:09:18 +00:00
|
|
|
The include file <bsd.subdir.mk> contains the default targets for building
|
|
|
|
subdirectories. It has the same seven targets as <bsd.prog.mk>: all, clean,
|
2017-11-17 18:16:46 +00:00
|
|
|
cleandir, depend, install, and tags. For all of the directories listed in the
|
|
|
|
variable SUBDIRS, the specified directory will be visited and the target made.
|
|
|
|
There is also a default target which allows the command "make subdir" where
|
|
|
|
subdir is any directory listed in the variable SUBDIRS.
|
1994-05-30 19:09:18 +00:00
|
|
|
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|
|
|
|
|
2017-11-17 18:16:46 +00:00
|
|
|
The include file <bsd.lib.mk> has support for building libraries. It has the
|
|
|
|
same seven targets as <bsd.prog.mk>: all, clean, cleandir, depend, install, and
|
|
|
|
tags. It has a limited number of suffixes, consistent with the current needs of
|
|
|
|
the BSD tree.
|
1994-05-30 19:09:18 +00:00
|
|
|
|
|
|
|
It sets/uses the following variables:
|
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
LDADD Additional loader objects.
|
|
|
|
|
2016-04-15 18:49:26 +00:00
|
|
|
LIB The name of the library to build. Both a shared and static
|
|
|
|
library will be built. NO_PIC can be set to only build a
|
|
|
|
static library.
|
2015-03-17 15:21:01 +00:00
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
LIBADD Additional libraries. This is for base system libraries
|
|
|
|
and is only valid inside of the /usr/src tree.
|
2017-03-08 05:49:58 +00:00
|
|
|
Use LIBADD=name instead of LDADD=-lname.
|
2015-03-17 15:21:01 +00:00
|
|
|
|
1994-05-30 19:09:18 +00:00
|
|
|
LIBDIR Target directory for libraries.
|
|
|
|
|
|
|
|
LIBGRP Library group.
|
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
LIBMODE Library mode.
|
|
|
|
|
1994-05-30 19:09:18 +00:00
|
|
|
LIBOWN Library owner.
|
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
LIBRARIES_ONLY Do not build or install files other than the library.
|
1994-05-30 19:09:18 +00:00
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
LIB_CXX The name of the library to build. It also causes
|
|
|
|
<bsd.lib.mk> to link the library with the
|
|
|
|
standard C++ library. LIB_CXX overrides the value
|
|
|
|
of LIB if LIB is also set. Both a shared and static library
|
|
|
|
will be built. NO_PIC can be set to only build a static
|
|
|
|
library.
|
1994-05-30 19:09:18 +00:00
|
|
|
|
2018-06-29 16:07:56 +00:00
|
|
|
LINKS The list of binary links; should be full pathnames, the
|
|
|
|
linked-to file coming first, followed by the linked
|
|
|
|
file. The files are hard-linked. For example, to link
|
|
|
|
/bin/test and /bin/[, use:
|
|
|
|
|
|
|
|
LINKS= /bin/test /bin/[
|
|
|
|
|
|
|
|
LINKOWN Owner of links created with LINKS [${LIBOWN}].
|
|
|
|
|
|
|
|
LINKGRP Group of links created with LINKS [${LIBGRP}].
|
|
|
|
|
|
|
|
LINKMODE Mode of links created with LINKS [${LIBMODE}].
|
|
|
|
|
2017-03-07 17:53:53 +00:00
|
|
|
MAN The manual pages to be installed. See bsd.man.mk for more
|
|
|
|
details.
|
1994-05-30 19:09:18 +00:00
|
|
|
|
2016-04-15 18:49:26 +00:00
|
|
|
SHLIB Like LIB but only builds a shared library.
|
|
|
|
|
|
|
|
SHLIB_CXX Like LIB_CXX but only builds a shared library.
|
|
|
|
|
2012-05-07 09:00:30 +00:00
|
|
|
SHLIB_LDSCRIPT Template file to generate shared library linker script.
|
2017-03-08 05:49:58 +00:00
|
|
|
If not defined, a simple symlink is created to the real
|
2012-05-07 09:00:30 +00:00
|
|
|
shared object.
|
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
SRCS List of source files to build the library. Suffix types
|
|
|
|
.s, .c, and .f are supported. Note, .s files are preferred
|
|
|
|
to .c files of the same name. (This is not the default for
|
|
|
|
versions of make.)
|
2013-01-17 17:27:10 +00:00
|
|
|
|
2001-03-28 15:12:29 +00:00
|
|
|
The include file <bsd.lib.mk> includes the file named "../Makefile.inc"
|
|
|
|
if it exists, as well as the include file <bsd.man.mk>.
|
1994-05-30 19:09:18 +00:00
|
|
|
|
|
|
|
It has rules for building profiled objects; profiled libraries are
|
|
|
|
built by default.
|
|
|
|
|
|
|
|
Libraries are ranlib'd before installation.
|
2014-03-15 09:27:59 +00:00
|
|
|
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|
|
|
|
|
|
|
|
The include file <bsd.test.mk> handles building one or more test programs
|
|
|
|
intended to be used in the FreeBSD Test Suite under /usr/tests/.
|
|
|
|
|
|
|
|
It has seven targets:
|
|
|
|
|
|
|
|
all:
|
|
|
|
build the test programs.
|
2016-02-07 18:40:04 +00:00
|
|
|
check:
|
Add limited sandbox capability to "make check"
== Rationale ==
r295380 introduced "make check" and consolidated means for running
test code in an attempt to simplify running tests. One could either
install files/libraries/programs and run "make check", or run "make check"
with an explicit CHECKDIR, e.g., `make check CHECKDIR=$(make -V.OBJDIR)``.
One criticism that was received is that "make check" should be run with
the intent of making dev->test->commit easier, which means that the target
audience's workflow should be developers. One developer pattern available
in other opensource projects is to run test code from a developer sandbox,
instead of installing to a system.
== Method ==
This approach is slightly different from the standard approach, in the sense
that it builds and installs into a deterministic directory under .OBJDIR (as I call it,
the "sandbox"), then runs "make check" against that. In the event the test
run is successful, the deterministic directory is removed to save space.
== Approach ==
bsd.lib.mk, bsd.prog.mk:
To support this functionality, a new variable `HAS_TESTS` is being added.
HAS_TESTS enables appropriate behavior with bsd.lib.mk and bsd.prog.mk, as
follows:
- Add "make check" as an available target from the directory.
- Pass down appropriate variables via ${TESTS_ENV}, i.e.,
${TESTS_LD_LIBRARY_PATH} and ${TESTS_PATH}.
One should add "HAS_TESTS" to directories containing tests in them, e.g. from
bin/sh/Makefile,
HAS_TESTS=
SUBDIR.${MK_TESTS}+= tests
HAS_TESTS doesn't automatically add the tests subdirectory for flexibility
reasons.
bsd.opts.mk, src.opts.mk:
- The knob ${MK_MAKE_CHECK_USE_SANDBOX} has been added, both to explicitly
direct (internally) when to set a deterministic ${DESTDIR} and to also allow
users to disable this behavior globally, i.e., via src.conf.
- MK_TESTS has been promoted from src.opts.mk to bsd.opts.mk to leverage
syntactic sugar for having MK_TESTS be a dependency for
MK_MAKE_CHECK_USE_SANDBOX, but to also ensure that src.opts.mk isn't required
to use suite.test.mk (which is a dependency of bsd.test.mk).
suite.test.mk:
- beforecheck behavior (when MK_MAKE_CHECK_USE_SANDBOX is enabled) is modified
from a no-op to:
-- Build.
-- Run "make hierarchy" on the sandbox dir.
-- Install the tests/files to the sandbox dir.
- aftercheck behavior (when MK_MAKE_CHECK_USE_SANDBOX is enabled) is modified
from a no-op to:
-- Remove the sandbox dir.
Again, because the dependency order set in bsd.test.mk is
beforecheck -> check -> aftercheck, "make check" will not be run unless
"beforecheck" completes successfully, and "aftercheck" will not be run unless
"beforecheck" and "check" complete successfully.
== Caveats ==
- This target must either be run with MK_INSTALL_AS_USER or as root. Otherwise
it will fail when running "make install" as the default user/group for many
makefiles when calling INSTALL is root/wheel.
- This target must be run from a suitable top-level directory. For example,
running tests from `tests/sys/fs/tmpfs` won't work, but `tests/sys/fs` will,
because `tests/sys/fs/tmpfs` relies on files installed by `tests/sys/fs`.
- Running MK_INSTALL_AS_USER may introduce determinism issues. However, using
it could identify deficiences in tests in terms of needing to be run as
root, which are not properly articulated in the test requirements.
- The doesn't negate the need for running "make installworld" and
"make checkworld", etc. Again, this just is intended to simplify the
dev->test->commit workflow.
== Cleanup done ==
- CHECKDIR is removed; one can use "MK_MAKE_CHECK_USE_SANDBOX=no" to enable
"legacy" (r295380) behavior.
MFC after: 2 months
Relnotes: yes (CHECKDIR removed; "make check" behavior changed)
Requested by: jhb
Reviewed by: arch (silence), testing (silence)
Differential Revision: D11905
2017-08-14 19:03:05 +00:00
|
|
|
runs the test programs with kyua test.
|
2016-02-07 18:40:04 +00:00
|
|
|
|
|
|
|
The beforecheck and aftercheck targets will be invoked, if
|
|
|
|
defined, to execute commands before and after the realcheck
|
|
|
|
target has been executed, respectively.
|
|
|
|
|
|
|
|
The devel/kyua package must be installed before invoking this
|
|
|
|
target.
|
2014-03-15 09:27:59 +00:00
|
|
|
clean:
|
|
|
|
remove the test programs and any object files.
|
|
|
|
cleandir:
|
|
|
|
remove all of the files removed by the target clean, as
|
|
|
|
well as .depend and tags.
|
|
|
|
depend:
|
|
|
|
make the dependencies for the source files, and store
|
|
|
|
them in the file .depend.
|
|
|
|
install:
|
|
|
|
install the test programs and their data files; if the
|
|
|
|
Makefile does not itself define the target install, the
|
|
|
|
targets beforeinstall and afterinstall may also be used
|
|
|
|
to cause actions immediately before and after the
|
|
|
|
install target is executed.
|
|
|
|
tags:
|
|
|
|
create a tags file for the source files.
|
|
|
|
|
|
|
|
It sets/uses the following variables, among many others:
|
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
ATF_TESTS_C The names of the ATF C test programs to build.
|
2015-10-11 21:29:24 +00:00
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
ATF_TESTS_CXX The names of the ATF C++ test programs to build.
|
2014-03-15 09:27:59 +00:00
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
ATF_TESTS_SH The names of the ATF sh test programs to build.
|
2015-10-11 21:29:24 +00:00
|
|
|
|
2019-02-20 01:12:59 +00:00
|
|
|
GTESTS The names of the GoogleTest test programs to build.
|
|
|
|
|
2014-03-15 09:27:59 +00:00
|
|
|
KYUAFILE If 'auto' (the default), generate a Kyuafile out of the
|
|
|
|
test programs defined in the Makefile. If 'yes', then a
|
|
|
|
manually-crafted Kyuafile must be supplied with the
|
|
|
|
sources. If 'no', no Kyuafile is installed (useful for
|
|
|
|
subdirectories providing helper programs or data files
|
|
|
|
only).
|
|
|
|
|
2015-12-20 06:27:36 +00:00
|
|
|
LOCALBASE The --prefix for the kyua package.
|
|
|
|
|
|
|
|
The value of LOCALBASE defaults to /usr/local .
|
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
NOT_FOR_TEST_SUITE
|
|
|
|
If defined, none of the built test programs get
|
|
|
|
installed under /usr/tests/ and no Kyuafile is
|
|
|
|
automatically generated. Should not be used within the
|
|
|
|
FreeBSD source tree but is provided for the benefit of
|
|
|
|
third-parties.
|
2014-03-15 09:27:59 +00:00
|
|
|
|
|
|
|
PLAIN_TESTS_C The names of the plain (legacy) programs to build.
|
|
|
|
|
|
|
|
PLAIN_TESTS_CXX The names of the plain (legacy) test programs to build.
|
|
|
|
|
|
|
|
PLAIN_TESTS_SH The names of the plain (legacy) test programs to build.
|
|
|
|
|
2014-03-16 01:22:23 +00:00
|
|
|
TAP_PERL_INTERPRETER
|
|
|
|
Path to the Perl interpreter to be used for
|
|
|
|
TAP-compliant test programs that are written in Perl.
|
|
|
|
Refer to TAP_TESTS_PERL for details.
|
|
|
|
|
2014-03-15 09:27:59 +00:00
|
|
|
TAP_TESTS_C The names of the TAP-compliant C test programs to build.
|
|
|
|
|
|
|
|
TAP_TESTS_CXX The names of the TAP-compliant C++ test programs to
|
|
|
|
build.
|
|
|
|
|
2014-03-16 01:22:23 +00:00
|
|
|
TAP_TESTS_PERL The names of the TAP-compliant Perl test programs to
|
|
|
|
build. The corresponding source files should end with
|
|
|
|
the .pl extension; the test program is marked as
|
|
|
|
requiring Perl; and TAP_PERL_INTERPRETER is used in the
|
|
|
|
built scripts as the interpreter of choice.
|
|
|
|
|
2014-03-15 09:27:59 +00:00
|
|
|
TAP_TESTS_SH The names of the TAP-compliant sh test programs to
|
|
|
|
build.
|
|
|
|
|
2017-03-07 17:38:52 +00:00
|
|
|
TESTSBASE Installation prefix for tests. Defaults to /usr/tests
|
|
|
|
|
|
|
|
TESTSDIR Path to the installed tests. Must be a subdirectory of
|
|
|
|
TESTSBASE and the subpath should match the relative
|
|
|
|
location of the tests within the src tree.
|
|
|
|
|
|
|
|
The value of TESTSDIR defaults to
|
|
|
|
${TESTSBASE}/${RELDIR:H} , e.g. /usr/tests/bin/ls when
|
|
|
|
included from bin/ls/tests .
|
|
|
|
|
2014-03-15 09:27:59 +00:00
|
|
|
TESTS_SUBDIRS List of subdirectories containing tests into which to
|
|
|
|
recurse. Differs from SUBDIR in that these directories
|
|
|
|
get registered into the automatically-generated
|
|
|
|
Kyuafile (if any).
|
|
|
|
|
|
|
|
The actual building of the test programs is performed by <bsd.prog.mk>.
|
|
|
|
Please see the documentation above for this other file for additional
|
|
|
|
details on the behavior of <bsd.test.mk>.
|