2013-12-06 12:04:52 +01:00
|
|
|
# $NetBSD: Makefile.mdset,v 1.38 2013/08/15 12:39:28 joerg Exp $
|
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
|
|
|
#
|
|
|
|
# Makefile snippet to ${TOOL_MDSETIMAGE} file system images into kernels
|
|
|
|
#
|
|
|
|
|
|
|
|
#
|
|
|
|
# Required variables:
|
|
|
|
# NETBSDSRCDIR Top level of src tree (set by <bsd.own.mk>)
|
|
|
|
# MDSETTARGETS List of images to ${TOOL_MDSETIMAGE} into kernels,
|
|
|
|
# containing one or more tuples of the form:
|
|
|
|
# KERNEL IMAGE FILENAME
|
|
|
|
#
|
|
|
|
# The kernel is ${TOOL_MDSETIMAGE} with ${IMAGE},
|
|
|
|
# ${STRIP}ped (after the symbols are stored in
|
|
|
|
# ${FILENAME}.symbols.gz), and gzipped into
|
|
|
|
# ${FILENAME}.gz.
|
|
|
|
#
|
|
|
|
# If KERNEL does not contain a `/', use
|
|
|
|
# ${KERNOBJDIR}/KERNEL/netbsd as the kernel.
|
|
|
|
#
|
|
|
|
# If FILENAME is "-", use "netbsd-${KERNEL}" as
|
|
|
|
# the target name. This may not be a sensible
|
|
|
|
# name if KERNEL contains a `/'.
|
|
|
|
#
|
|
|
|
# Optional variables:
|
|
|
|
# MDSET_RELEASEDIR Where to install release kernels.
|
|
|
|
#
|
|
|
|
# MDSET_NOGZIP If defined, don't gzip any kernels.
|
|
|
|
#
|
|
|
|
# MDSET_NOGZIP.${FILENAME} If defined, don't gzip ${FILENAME}
|
|
|
|
#
|
|
|
|
# MDSET_NOIMAGE.${FILENAME} If defined, don't add ${IMAGE} to
|
|
|
|
# ${FILENAME}
|
|
|
|
#
|
|
|
|
# MDSET_NOSTRIP If defined, don't strip any kernels.
|
|
|
|
#
|
|
|
|
# MDSET_NOSTRIP.${FILENAME} If defined, don't strip ${FILENAME}
|
|
|
|
#
|
|
|
|
# MDSET_NOSYMBOLS If defined, don't generate *.symbols.gz
|
|
|
|
#
|
|
|
|
# MDSET_NOSYMBOLS.${FILENAME} If defined, don't generate
|
|
|
|
# ${FILENAME}.symbols.gz
|
|
|
|
#
|
|
|
|
# MDSET_POST For each kernel,
|
|
|
|
# execute this after ${NM} / ${STRIP}.
|
|
|
|
# Kernel is available as "${.TARGET}"
|
|
|
|
#
|
|
|
|
# MDSET_POST.${FILENAME} For each kernel named ${FILENAME},
|
|
|
|
# execute this after ${NM} / ${STRIP}.
|
|
|
|
# Kernel is available as "${.TARGET}"
|
|
|
|
#
|
|
|
|
# MDSET_SUFFIXES.${FILENAME} List of extra install kernel suffixes
|
|
|
|
# and build commands to create from
|
|
|
|
# ${FILENAME} after its created by
|
|
|
|
# ${TOOL_MDSETIMAGE} ; ${NM} ; ${STRIP}:
|
|
|
|
# SUFFIX COMMANDVAR
|
|
|
|
# "${.TARGET}" is "${FILENAME}.${SUFFIX}"
|
|
|
|
# COMMANDVAR is the name of the variable
|
|
|
|
# containing the command to build
|
|
|
|
# ${.TARGET}.
|
|
|
|
#
|
|
|
|
# Variables modified by this:
|
|
|
|
# KERNELS List of kernel .gz files to build
|
|
|
|
# KERNELSYMS List of kernel .symbol.gz files to build
|
|
|
|
#
|
|
|
|
|
|
|
|
.if !defined(_MAKEFILE_MDSET_)
|
|
|
|
_MAKEFILE_MDSET_=1
|
|
|
|
|
|
|
|
.include <bsd.kernobj.mk>
|
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
# The default is to build for all MDSETTARGETS
|
|
|
|
ALL_KERNELS?= +
|
|
|
|
|
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
|
|
|
.for _K _I _F in ${MDSETTARGETS} # {
|
2013-12-06 12:04:52 +01:00
|
|
|
.for currentsel in ${ALL_KERNELS} # {
|
|
|
|
.if ${currentsel} == "+" || ${_K} == ${currentsel}
|
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
|
|
|
|
|
|
|
_KERNEL:=${_K} # (work around obscure issue in make(1))
|
|
|
|
.if (${_KERNEL:M*/*} != "")
|
|
|
|
_KERNNAME.${_K}.${_F}:= ${_K}
|
|
|
|
.else
|
|
|
|
_KERNNAME.${_K}.${_F}:= ${KERNOBJDIR}/${_K}/netbsd
|
|
|
|
.endif
|
|
|
|
|
|
|
|
_FILENAME:=${_F} # (work around obscure issue in make(1))
|
|
|
|
.if ${_FILENAME} == "-"
|
|
|
|
_KERNEL.${_K}.${_F}:= netbsd-${_K}
|
|
|
|
_FILENAME:= ${_KERNEL.${_K}.${_F}}
|
|
|
|
.else
|
|
|
|
_KERNEL.${_K}.${_F}:= ${_F}
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.for _S _C in ${MDSET_SUFFIXES.${_F}} # {
|
|
|
|
CLEANFILES+= ${_KERNEL.${_K}.${_F}}.${_S}
|
|
|
|
|
|
|
|
${_KERNEL.${_K}.${_F}}.${_S}: ${_KERNEL.${_K}.${_F}}
|
|
|
|
.if defined(${_C})
|
|
|
|
${${_C}}
|
|
|
|
.else
|
|
|
|
@echo "No such variable \"${_C}\""
|
|
|
|
false
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if defined(MDSET_NOGZIP.${_FILENAME}) && defined(MDSET_NOGZIP)
|
|
|
|
KERNELS+= ${_KERNEL.${_K}.${_F}}.${_S}
|
|
|
|
.else # {
|
|
|
|
KERNELS+= ${_KERNEL.${_K}.${_F}}.${_S}.gz
|
|
|
|
|
|
|
|
${_KERNEL.${_K}.${_F}}.${_S}.gz: ${_KERNEL.${_K}.${_F}}.${_S}
|
|
|
|
${_MKTARGET_CREATE}
|
|
|
|
-rm -f ${.TARGET}
|
|
|
|
gzip -9nc ${.ALLSRC} > ${.TARGET}
|
|
|
|
.endif # }
|
|
|
|
|
|
|
|
.endfor # }
|
|
|
|
|
|
|
|
.if !defined(MDSET_NOSYMBOLS.${_FILENAME}) && !defined(MDSET_NOSYMBOLS)
|
|
|
|
KERNELSYMS+= ${_KERNEL.${_K}.${_F}}.symbols.gz
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if defined(MDSET_POST.${_FILENAME})
|
|
|
|
_POST.${_KERNEL.${_K}.${_F}}:= ${MDSET_POST.${_FILENAME}}
|
|
|
|
.elif defined(MDSET_POST)
|
|
|
|
_POST.${_KERNEL.${_K}.${_F}}:= ${MDSET_POST}
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
|
|
CLEANFILES+= ${_KERNEL.${_K}.${_F}}
|
|
|
|
|
|
|
|
.if defined(MDSET_NOIMAGE.${_FILENAME})
|
|
|
|
${_I}=
|
|
|
|
.endif
|
|
|
|
|
|
|
|
# Darwin requires a special hack - this is documented in
|
|
|
|
# doc/HACKS, and just works around the problems described more
|
|
|
|
# fully in http://mail-index.netbsd.org/current-users/2008/06/27/msg003242.html
|
|
|
|
OPSYS!= uname -s
|
|
|
|
.if ${OPSYS} == "Darwin"
|
|
|
|
MDSETIMAGEFLAGS=
|
|
|
|
.else
|
|
|
|
MDSETIMAGEFLAGS=-v
|
|
|
|
.endif
|
|
|
|
|
|
|
|
${_KERNEL.${_K}.${_F}}: .NOTMAIN ${_KERNNAME.${_K}.${_F}} ${_I}
|
|
|
|
${_MKTARGET_CREATE} "(from: ${.ALLSRC})"
|
|
|
|
@rm -f ${.TARGET} ${.TARGET}.tmp ${.TARGET}.symbols.gz
|
|
|
|
@cp ${_KERNNAME.${_K}.${_F}} ${.TARGET}.tmp
|
|
|
|
.if !defined(MDSET_NOIMAGE.${_FILENAME})
|
|
|
|
${TOOL_MDSETIMAGE} ${MDSETIMAGEFLAGS} ${.TARGET}.tmp ${_I}
|
|
|
|
.endif
|
|
|
|
.if !defined(MDSET_NOSYMBOLS.${_FILENAME}) && !defined(MDSET_NOSYMBOLS)
|
|
|
|
${NM} ${.TARGET}.tmp | gzip -9n > ${.TARGET}.symbols.gz
|
|
|
|
.endif
|
|
|
|
.if !defined(MDSET_NOSTRIP.${_FILENAME}) && !defined(MDSET_NOSTRIP)
|
2013-12-06 12:04:52 +01:00
|
|
|
${STRIP} -R .eh_frame -R .eh_frame_hdr -R .comment -R .ident ${.TARGET}.tmp
|
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
|
|
|
.endif
|
|
|
|
@mv ${.TARGET}.tmp ${.TARGET}
|
|
|
|
.if defined(MDSET_POST.${_FILENAME}) || defined(MDSET_POST)
|
|
|
|
${_POST.${.TARGET}}
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if defined(MDSET_NOGZIP.${_FILENAME}) || defined(MDSET_NOGZIP)
|
|
|
|
KERNELS+= ${_KERNEL.${_K}.${_F}}
|
|
|
|
.else # {
|
|
|
|
KERNELS+= ${_KERNEL.${_K}.${_F}}.gz
|
|
|
|
|
|
|
|
${_KERNEL.${_K}.${_F}}.gz: ${_KERNEL.${_K}.${_F}}
|
|
|
|
${_MKTARGET_CREATE}
|
|
|
|
-rm -f ${.TARGET}
|
|
|
|
gzip -9nc ${.ALLSRC} > ${.TARGET}
|
|
|
|
.endif # }
|
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
.endif
|
|
|
|
.endfor # }
|
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
|
|
|
.endfor # }
|
|
|
|
|
|
|
|
CLEANFILES+= ${KERNELS} ${KERNELSYMS}
|
|
|
|
|
|
|
|
realall: ${KERNELS}
|
|
|
|
|
|
|
|
.if defined(MDSET_RELEASEDIR)
|
|
|
|
release:: check_RELEASEDIR .WAIT ${KERNELS}
|
2013-12-06 12:04:52 +01:00
|
|
|
test -z "${KERNELS}" || \
|
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
|
|
|
${RELEASE_INSTALL} ${KERNELS} ${KERNELSYMS} \
|
|
|
|
${RELEASEDIR}/${RELEASEMACHINEDIR}/${MDSET_RELEASEDIR}
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
|
|
.endif # _MAKEFILE_MDSET_
|