Add bsd.man.mk references for MAN under bsd.lib.mk and bsd.prog.mk

The latter set of manpages directly consume bsd.man.mk, so the bsd.man.mk
behavior should be the source of truth for underlying behavior, whereas
the other manpage fragment descriptions should document how they tweak
the variable behavior, if at all (bsd.prog.mk does tweak the default
value, as noted in its description)

MFC after:	1 week
Sponsored by:	Dell EMC Isilon
This commit is contained in:
Enji Cooper 2017-03-07 17:53:53 +00:00
parent 426dc38921
commit 67833f2936
Notes: svn2git 2020-12-20 02:59:44 +00:00
svn path=/head/; revision=314872

View File

@ -320,8 +320,8 @@ LINKS The list of binary links; should be full pathnames, the
LINKS= /bin/test /bin/[
MAN Manual pages (should end in .1 - .9). If no MAN variable
is defined, "MAN=${PROG}.1" is assumed.
MAN Manual pages. If no MAN variable is defined,
"MAN=${PROG}.1" is assumed. See bsd.man.mk for more details.
PROG The name of the program to build. If not supplied, nothing
is built.
@ -532,7 +532,8 @@ LIB_CXX The name of the library to build. It also causes
LINTLIBDIR Target directory for lint libraries.
MAN The manual pages to be installed (use a .1 - .9 suffix).
MAN The manual pages to be installed. See bsd.man.mk for more
details.
SHLIB Like LIB but only builds a shared library.