Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
# $NetBSD: bsd.man.mk,v 1.109 2011/09/10 16:57:35 apb Exp $
|
2010-02-24 12:58:05 +01:00
|
|
|
# @(#)bsd.man.mk 8.1 (Berkeley) 6/8/93
|
|
|
|
|
2010-06-25 20:29:09 +02:00
|
|
|
.include <bsd.init.mk>
|
2010-02-24 12:58:05 +01:00
|
|
|
|
|
|
|
##### Basic targets
|
2012-02-16 02:48:46 +01:00
|
|
|
.PHONY: catinstall maninstall catpages manpages catlinks manlinks
|
|
|
|
.PHONY: htmlinstall htmlpages htmllinks
|
2010-02-24 12:58:05 +01:00
|
|
|
.PHONY: lintmanpages
|
|
|
|
realinstall: ${MANINSTALL}
|
|
|
|
|
|
|
|
##### Default values
|
2012-02-16 02:48:46 +01:00
|
|
|
.if ${USETOOLS} == "yes"
|
|
|
|
TMACDEPDIR?= ${TOOLDIR}/share/groff/tmac
|
|
|
|
.else
|
|
|
|
TMACDEPDIR?= /usr/share/tmac
|
|
|
|
.endif
|
|
|
|
|
|
|
|
HTMLDIR?= ${DESTDIR}${MANDIR}
|
|
|
|
CATDEPS?= ${TMACDEPDIR}/andoc.tmac \
|
|
|
|
${TMACDEPDIR}/doc.tmac \
|
|
|
|
${TMACDEPDIR}/mdoc/doc-common \
|
|
|
|
${TMACDEPDIR}/mdoc/doc-ditroff \
|
|
|
|
${TMACDEPDIR}/mdoc/doc-nroff \
|
|
|
|
${TMACDEPDIR}/mdoc/doc-syms
|
|
|
|
MANTARGET?= cat
|
|
|
|
|
|
|
|
MAN?=
|
|
|
|
MLINKS?=
|
|
|
|
_MNUMBERS= 1 2 3 4 5 6 7 8 9
|
|
|
|
.SUFFIXES: ${_MNUMBERS:@N@.$N@}
|
|
|
|
|
|
|
|
.if ${MKMANZ} == "no"
|
|
|
|
MANCOMPRESS?=
|
|
|
|
MANSUFFIX?=
|
|
|
|
.else
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
MANCOMPRESS?= ${TOOL_GZIP} -ncf
|
2012-02-16 02:48:46 +01:00
|
|
|
MANSUFFIX?= .gz
|
|
|
|
.endif
|
2010-02-24 12:58:05 +01:00
|
|
|
|
|
|
|
# make MANCOMPRESS a filter, so it can be inserted on an as-needed basis
|
|
|
|
.if !empty(MANCOMPRESS)
|
|
|
|
MANCOMPRESS:= | ${MANCOMPRESS}
|
|
|
|
.endif
|
|
|
|
|
|
|
|
__installpage: .USE
|
|
|
|
@cmp -s ${.ALLSRC} ${.TARGET} > /dev/null 2>&1 || \
|
|
|
|
(${_MKSHMSG_INSTALL} ${.TARGET}; \
|
|
|
|
${_MKSHECHO} "${INSTALL_FILE} -o ${MANOWN} -g ${MANGRP} -m ${MANMODE} \
|
|
|
|
${.ALLSRC} ${.TARGET}" && \
|
|
|
|
${INSTALL_FILE} -o ${MANOWN} -g ${MANGRP} -m ${MANMODE} \
|
|
|
|
${.ALLSRC} ${.TARGET})
|
|
|
|
|
|
|
|
# XXX consider including bsd.links.mk and using __linkinstall instead
|
|
|
|
__linkinstallpage: .USE
|
|
|
|
${_MKSHMSG_INSTALL} ${.TARGET}; \
|
|
|
|
${_MKSHECHO} "${INSTALL_LINK} -o ${MANOWN} -g ${MANGRP} -m ${MANMODE} \
|
|
|
|
${.ALLSRC} ${.TARGET}" && \
|
|
|
|
${INSTALL_LINK} -o ${MANOWN} -g ${MANGRP} -m ${MANMODE} \
|
|
|
|
${.ALLSRC} ${.TARGET}
|
|
|
|
|
|
|
|
##### Build and install rules (source form pages)
|
|
|
|
|
|
|
|
.if ${MKMAN} != "no"
|
|
|
|
maninstall: manpages manlinks
|
|
|
|
manpages:: # ensure target exists
|
|
|
|
MANPAGES= ${MAN:C/.$/&${MANSUFFIX}/}
|
|
|
|
|
|
|
|
realall: ${MANPAGES}
|
|
|
|
.if !empty(MANSUFFIX)
|
|
|
|
.NOPATH: ${MANPAGES}
|
|
|
|
.SUFFIXES: ${_MNUMBERS:@N@.$N${MANSUFFIX}@}
|
|
|
|
|
|
|
|
${_MNUMBERS:@N@.$N.$N${MANSUFFIX}@}: # build rule
|
|
|
|
${_MKTARGET_FORMAT}
|
|
|
|
cat ${.IMPSRC} ${MANCOMPRESS} > ${.TARGET}.tmp && mv ${.TARGET}.tmp ${.TARGET}
|
|
|
|
.endif # !empty(MANSUFFIX)
|
|
|
|
|
|
|
|
.for F in ${MANPAGES:S/${MANSUFFIX}$//:O:u}
|
|
|
|
_F:= ${DESTDIR}${MANDIR}/man${F:T:E}${MANSUBDIR}/${F}${MANSUFFIX}
|
|
|
|
|
|
|
|
.if ${MKUPDATE} == "no"
|
|
|
|
${_F}! ${F}${MANSUFFIX} __installpage # install rule
|
|
|
|
.if !defined(BUILD) && !make(all) && !make(${F})
|
|
|
|
${_F}! .MADE # no build at install
|
|
|
|
.endif
|
|
|
|
.else
|
|
|
|
${_F}: ${F}${MANSUFFIX} __installpage # install rule
|
|
|
|
.if !defined(BUILD) && !make(all) && !make(${F})
|
|
|
|
${_F}: .MADE # no build at install
|
|
|
|
.endif
|
|
|
|
.endif
|
|
|
|
|
|
|
|
manpages:: ${_F}
|
|
|
|
.PRECIOUS: ${_F} # keep if install fails
|
|
|
|
.endfor
|
|
|
|
|
|
|
|
manlinks:: # link install
|
|
|
|
|
|
|
|
.for _src _dst in ${MLINKS}
|
|
|
|
_l:=${DESTDIR}${MANDIR}/man${_src:T:E}${MANSUBDIR}/${_src}${MANSUFFIX}
|
|
|
|
_t:=${DESTDIR}${MANDIR}/man${_dst:T:E}${MANSUBDIR}/${_dst}${MANSUFFIX}
|
|
|
|
|
|
|
|
# Handle case conflicts carefully, when _dst occurs
|
|
|
|
# more than once after case flattening
|
|
|
|
.if ${MKUPDATE} == "no" || ${MLINKS:tl:M${_dst:tl:Q}:[\#]} > 1
|
|
|
|
${_t}! ${_l} __linkinstallpage
|
|
|
|
.else
|
|
|
|
${_t}: ${_l} __linkinstallpage
|
|
|
|
.endif
|
|
|
|
|
|
|
|
manlinks:: ${_t}
|
|
|
|
.PRECIOUS: ${_t}
|
|
|
|
.endfor
|
|
|
|
.endif # ${MKMAN} != "no"
|
|
|
|
|
2012-02-16 02:48:46 +01:00
|
|
|
##### Build and install rules (plaintext pages)
|
|
|
|
|
|
|
|
.if (${MKCATPAGES} != "no") && (${MKMAN} != "no")
|
|
|
|
catinstall: catpages catlinks
|
|
|
|
catpages:: # ensure target exists
|
|
|
|
CATPAGES= ${MAN:C/\.([1-9])$/.cat\1${MANSUFFIX}/}
|
|
|
|
|
|
|
|
realall: ${CATPAGES}
|
|
|
|
.NOPATH: ${CATPAGES}
|
|
|
|
.SUFFIXES: ${_MNUMBERS:@N@.cat$N${MANSUFFIX}@}
|
|
|
|
.MADE: ${CATDEPS}
|
|
|
|
|
|
|
|
${_MNUMBERS:@N@.$N.cat$N${MANSUFFIX}@}: ${CATDEPS} # build rule
|
|
|
|
${_MKTARGET_FORMAT}
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
.if ${MKMANDOC} == yes && !defined(NOMANDOC)
|
2012-02-16 02:48:46 +01:00
|
|
|
if test ""${NOMANDOC.${.IMPSRC:T}:tl:Q} != "yes"; then \
|
|
|
|
${TOOL_MANDOC_ASCII} ${.IMPSRC} ${MANCOMPRESS} \
|
|
|
|
> ${.TARGET}.tmp && mv ${.TARGET}.tmp ${.TARGET}; \
|
|
|
|
else \
|
|
|
|
${TOOL_ROFF_ASCII} -mandoc ${.IMPSRC} ${MANCOMPRESS} \
|
|
|
|
> ${.TARGET}.tmp && mv ${.TARGET}.tmp ${.TARGET}; \
|
|
|
|
fi
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
.elif defined(USETBL)
|
|
|
|
${TOOL_TBL} ${.IMPSRC} | ${TOOL_ROFF_ASCII} -mandoc ${MANCOMPRESS} \
|
|
|
|
> ${.TARGET}.tmp && mv ${.TARGET}.tmp ${.TARGET}
|
2012-02-16 02:48:46 +01:00
|
|
|
.else
|
|
|
|
${TOOL_ROFF_ASCII} -mandoc ${.IMPSRC} ${MANCOMPRESS} \
|
|
|
|
> ${.TARGET}.tmp && mv ${.TARGET}.tmp ${.TARGET}
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.for F in ${CATPAGES:S/${MANSUFFIX}$//:O:u}
|
|
|
|
_F:= ${DESTDIR}${MANDIR}/${F:T:E}${MANSUBDIR}/${F:R}.0${MANSUFFIX}
|
|
|
|
|
|
|
|
.if ${MKUPDATE} == "no"
|
|
|
|
${_F}! ${F}${MANSUFFIX} __installpage # install rule
|
|
|
|
.if !defined(BUILD) && !make(all) && !make(${F})
|
|
|
|
${_F}! .MADE # no build at install
|
|
|
|
.endif
|
|
|
|
.else
|
|
|
|
${_F}: ${F}${MANSUFFIX} __installpage # install rule
|
|
|
|
.if !defined(BUILD) && !make(all) && !make(${F})
|
|
|
|
${_F}: .MADE # no build at install
|
|
|
|
.endif
|
|
|
|
.endif
|
|
|
|
|
|
|
|
catpages:: ${_F}
|
|
|
|
.PRECIOUS: ${_F} # keep if install fails
|
|
|
|
.endfor
|
|
|
|
|
|
|
|
catlinks:: # link install
|
|
|
|
|
|
|
|
.for _src _dst in ${MLINKS}
|
|
|
|
_l:=${DESTDIR}${MANDIR}/cat${_src:T:E}${MANSUBDIR}/${_src:R}.0${MANSUFFIX}
|
|
|
|
_t:=${DESTDIR}${MANDIR}/cat${_dst:T:E}${MANSUBDIR}/${_dst:R}.0${MANSUFFIX}
|
|
|
|
|
|
|
|
# Handle case conflicts carefully, when _dst occurs
|
|
|
|
# more than once after case flattening
|
|
|
|
.if ${MKUPDATE} == "no" || ${MLINKS:tl:M${_dst:tl:Q}:[\#]} > 1
|
|
|
|
${_t}! ${_l} __linkinstallpage
|
|
|
|
.else
|
|
|
|
${_t}: ${_l} __linkinstallpage
|
|
|
|
.endif
|
|
|
|
|
|
|
|
catlinks:: ${_t}
|
|
|
|
.PRECIOUS: ${_t}
|
|
|
|
.endfor
|
|
|
|
.endif # (${MKCATPAGES} != "no") && (${MKMAN} != "no")
|
|
|
|
|
|
|
|
##### Build and install rules (HTML pages)
|
|
|
|
|
|
|
|
.if (${MKHTML} != "no") && (${MKMAN} != "no") # {
|
|
|
|
htmlinstall: htmlpages htmllinks
|
|
|
|
htmlpages:: # ensure target exists
|
|
|
|
HTMLPAGES= ${MAN:C/\.([1-9])$/.html\1/}
|
|
|
|
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
HTMLLINKS= ${MANSUBDIR:?../:}../html%S/%N.html
|
|
|
|
HTMLSTYLE= ${MANSUBDIR:?../:}../style.css
|
|
|
|
|
2012-02-16 02:48:46 +01:00
|
|
|
realall: ${HTMLPAGES}
|
|
|
|
.NOPATH: ${HTMLPAGES}
|
|
|
|
.SUFFIXES: ${_MNUMBERS:@N@.html$N@}
|
|
|
|
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
${_MNUMBERS:@N@.$N.html$N@}: # build rule
|
2012-02-16 02:48:46 +01:00
|
|
|
${_MKTARGET_FORMAT}
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
${TOOL_MANDOC_HTML} -Oman=${HTMLLINKS} -Ostyle=${HTMLSTYLE} \
|
|
|
|
${.IMPSRC} > ${.TARGET}.tmp && \
|
2012-02-16 02:48:46 +01:00
|
|
|
mv ${.TARGET}.tmp ${.TARGET}
|
|
|
|
|
|
|
|
.for F in ${HTMLPAGES:O:u}
|
|
|
|
# construct installed path
|
|
|
|
_F:= ${HTMLDIR}/${F:T:E}${MANSUBDIR}/${F:R:S-/index$-/x&-}.html
|
|
|
|
|
|
|
|
.if ${MKUPDATE} == "no"
|
|
|
|
${_F}! ${F} __installpage # install rule
|
|
|
|
.if !defined(BUILD) && !make(all) && !make(${F})
|
|
|
|
${_F}! .MADE # no build at install
|
|
|
|
.endif
|
|
|
|
.else
|
|
|
|
${_F}: ${F} __installpage # install rule
|
|
|
|
.if !defined(BUILD) && !make(all) && !make(${F})
|
|
|
|
${_F}: .MADE # no build at install
|
|
|
|
.endif
|
|
|
|
.endif
|
|
|
|
|
|
|
|
htmlpages:: ${_F}
|
|
|
|
.PRECIOUS: ${_F} # keep if install fails
|
|
|
|
.endfor
|
|
|
|
|
|
|
|
htmllinks:: # link install
|
|
|
|
|
|
|
|
.for _src _dst in ${MLINKS}
|
|
|
|
_l:=${HTMLDIR}/html${_src:T:E}${MANSUBDIR}/${_src:R:S-/index$-/x&-}.html
|
|
|
|
_t:=${HTMLDIR}/html${_dst:T:E}${MANSUBDIR}/${_dst:R:S-/index$-/x&-}.html
|
|
|
|
|
|
|
|
# Handle case conflicts carefully, when _dst occurs
|
|
|
|
# more than once after case flattening
|
|
|
|
.if ${MKUPDATE} == "no" || ${MLINKS:tl:M${_dst:tl:Q}:[\#]} > 1
|
|
|
|
${_t}! ${_l} __linkinstallpage
|
|
|
|
.else
|
|
|
|
${_t}: ${_l} __linkinstallpage
|
|
|
|
.endif
|
|
|
|
|
|
|
|
htmllinks:: ${_t}
|
|
|
|
.PRECIOUS: ${_t}
|
|
|
|
.endfor
|
|
|
|
|
|
|
|
.endif # }
|
2010-02-24 12:58:05 +01:00
|
|
|
|
|
|
|
##### Clean rules
|
|
|
|
.undef _F
|
|
|
|
|
|
|
|
.if !empty(MAN) && (${MKMAN} != "no")
|
|
|
|
.if (${MKCATPAGES} != "no")
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
CLEANDIRFILES+= ${CATPAGES}
|
2010-02-24 12:58:05 +01:00
|
|
|
.endif
|
|
|
|
.if !empty(MANSUFFIX)
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
CLEANDIRFILES+= ${MANPAGES} ${CATPAGES:S/${MANSUFFIX}$//}
|
2010-02-24 12:58:05 +01:00
|
|
|
.endif
|
|
|
|
.if ${MKHTML} != "no"
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
CLEANDIRFILES+= ${HTMLPAGES}
|
2010-02-24 12:58:05 +01:00
|
|
|
.endif
|
|
|
|
.endif
|
|
|
|
# (XXX ${CATPAGES:S...} cleans up old .catN files where .catN.gz now used)
|
|
|
|
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
.if !empty(MANPAGES)
|
2012-02-16 02:48:46 +01:00
|
|
|
lintmanpages: ${MANPAGES}
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
${TOOL_MANDOC_LINT} -Tlint -fstrict -Wall,stop ${.ALLSRC}
|
2012-02-16 02:48:46 +01:00
|
|
|
.endif
|
2010-02-24 12:58:05 +01:00
|
|
|
|
|
|
|
##### Pull in related .mk logic
|
2010-06-25 20:29:09 +02:00
|
|
|
.include <bsd.obj.mk>
|
|
|
|
.include <bsd.files.mk>
|
|
|
|
.include <bsd.sys.mk>
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
.include <bsd.clean.mk>
|
2010-02-24 12:58:05 +01:00
|
|
|
|
|
|
|
${TARGETS} catinstall maninstall htmlinstall: # ensure existence
|