2013-12-06 12:04:52 +01:00
|
|
|
# $NetBSD: Makefile,v 1.170 2013/09/02 14:34:57 joerg Exp $
|
2012-06-06 16:46:00 +02:00
|
|
|
|
|
|
|
.include <bsd.own.mk>
|
2013-12-06 12:04:52 +01:00
|
|
|
.include <bsd.endian.mk>
|
2012-06-06 16:46:00 +02:00
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
# Make sure that the ordered build/install processing applies when using
|
|
|
|
# plain make.
|
|
|
|
.MAIN: build_install
|
|
|
|
|
|
|
|
# TOOLDIR must be valid, unless MKTOOLS=no
|
|
|
|
.if ${MKTOOLS:Uyes} != "no"
|
|
|
|
.if "${TOOLDIR}" == ""
|
|
|
|
.error "TOOLDIR is undefined or empty"
|
|
|
|
.elif "${TOOLDIR:tW:M/*}" == ""
|
|
|
|
.error "TOOLDIR is not an absolute path: ${TOOLDIR}"
|
|
|
|
#.elif !exists(TOOLDIR) # XXX .exists fails for directories
|
|
|
|
#.error "TOOLDIR does not exist: ${TOOLDIR}"
|
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
|
2013-12-06 12:04:52 +01:00
|
|
|
.endif # MKTOOLS != no
|
|
|
|
|
|
|
|
# TOOLS_BUILDRUMP == yes builds only the subset of the tools required
|
|
|
|
# for building rump kernels and the hypervisor. It is typically used
|
|
|
|
# when building rump kernels targeted for non-NetBSD systems (via
|
|
|
|
# buildrump.sh), and should not be set for a regular "make build".
|
|
|
|
TOOLS_BUILDRUMP?=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
|
|
|
|
|
|
|
.if ${TOOLCHAIN_MISSING} == "no"
|
2013-12-06 12:04:52 +01:00
|
|
|
.if defined(HAVE_GCC)
|
|
|
|
TOOLCHAIN_BITS= gmake .WAIT
|
|
|
|
.endif
|
|
|
|
|
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 defined(HAVE_GCC)
|
|
|
|
.if ${HAVE_GCC} >= 45
|
|
|
|
TOOLCHAIN_BITS+= gmp .WAIT
|
|
|
|
TOOLCHAIN_BITS+= mpfr .WAIT
|
|
|
|
TOOLCHAIN_BITS+= mpc .WAIT
|
|
|
|
.endif
|
|
|
|
.endif
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if ${TOOLCHAIN_MISSING} == "no"
|
|
|
|
TOOLCHAIN_BITS+= binutils .WAIT
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if defined(HAVE_GCC)
|
|
|
|
.if ${TOOLCHAIN_MISSING} == "no"
|
|
|
|
TOOLCHAIN_BITS+= gcc
|
2013-12-06 12:04:52 +01:00
|
|
|
. if ${MKCROSSGDB:Uno} != "no" # LSC: Doesn't work || make(obj)
|
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
|
|
|
TOOLCHAIN_BITS+= gdb
|
|
|
|
. endif
|
|
|
|
TOOLCHAIN_BITS+= .WAIT
|
|
|
|
.endif
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if defined(HAVE_PCC)
|
|
|
|
.if ${TOOLCHAIN_MISSING} == "no"
|
|
|
|
TOOLCHAIN_BITS+= pcc
|
|
|
|
.endif
|
|
|
|
.endif
|
|
|
|
|
2012-10-26 15:22:39 +02:00
|
|
|
.if !defined(__MINIX)
|
|
|
|
.if ${TOOLCHAIN_MISSING} == "no"
|
|
|
|
# XXX Eventually, we want to be able to build dbsym and mdsetimage
|
|
|
|
# XXX if EXTERNAL_TOOLCHAIN is set.
|
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
|
|
|
TOOLCHAIN_BITS+= dbsym mdsetimage
|
|
|
|
.endif
|
2012-10-26 15:22:39 +02:00
|
|
|
.endif # !defined(__MINIX)
|
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
|
|
|
|
|
|
|
DTRACE_BITS=
|
|
|
|
.if ${MKDTRACE} != "no"
|
|
|
|
DTRACE_BITS+= .WAIT libelf
|
|
|
|
DTRACE_BITS+= .WAIT libdwarf
|
2013-12-06 12:04:52 +01:00
|
|
|
DTRACE_BITS+= .WAIT libctf
|
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
|
|
|
DTRACE_BITS+= .WAIT ctfconvert ctfmerge
|
|
|
|
.endif
|
|
|
|
|
|
|
|
LINT_BITS=
|
|
|
|
.if ${MKLINT} != "no"
|
|
|
|
LINT_BITS= lint lint2
|
|
|
|
.endif
|
2012-06-06 16:46:00 +02:00
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
# All of host-mkdep, compat, and binstall are needed before anything
|
|
|
|
# else. Within this group, they must be built in a specific order, and
|
|
|
|
# all of them must be built before any of them is installed. They may
|
|
|
|
# be installed in any order. This can't be expressed using the .WAIT
|
|
|
|
# notation inside the SUBDIR list.
|
|
|
|
#
|
|
|
|
# XXX .ORDER does not work when multiple targets are passed on the
|
|
|
|
# make command line without "-j", so use dependencies in addition to .ORDER.
|
|
|
|
#
|
|
|
|
.ORDER: dependall-host-mkdep dependall-compat dependall-binstall
|
|
|
|
.if make(dependall-host-mkdep) && make(dependall-compat)
|
|
|
|
dependall-compat: dependall-host-mkdep
|
|
|
|
.endif
|
|
|
|
.if make(dependall-compat) && make(dependall-binstall)
|
|
|
|
dependall-binstall: dependall-compat
|
|
|
|
.endif
|
|
|
|
|
2012-06-06 16:46:00 +02:00
|
|
|
# Dependencies in SUBDIR below ordered to maximize parallel ability.
|
2013-12-06 12:04:52 +01:00
|
|
|
# See above for special treatment for host-mkdep, compat, and binstall.
|
|
|
|
#
|
|
|
|
SUBDIR= host-mkdep compat binstall \
|
|
|
|
.WAIT mktemp .WAIT sed .WAIT
|
|
|
|
.if ${TOOLS_BUILDRUMP} == "no"
|
|
|
|
SUBDIR+= genassym \
|
|
|
|
${LINT_BITS} \
|
|
|
|
makewhatis mtree nbperf .WAIT
|
|
|
|
.endif
|
|
|
|
|
|
|
|
SUBDIR+= join lorder m4 mkdep tsort .WAIT yacc .WAIT awk .WAIT lex
|
|
|
|
|
|
|
|
.if ${TOOLS_BUILDRUMP} == "no"
|
|
|
|
SUBDIR += .WAIT texinfo \
|
2012-06-06 16:46:00 +02:00
|
|
|
.WAIT tic \
|
2012-10-22 16:10:38 +02:00
|
|
|
.WAIT pax \
|
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
|
|
|
.WAIT ${TOOLCHAIN_BITS} \
|
2012-10-26 15:22:39 +02:00
|
|
|
${DTRACE_BITS} \
|
|
|
|
cat cksum \
|
|
|
|
file \
|
2015-09-11 11:48:57 +02:00
|
|
|
makefs .WAIT \
|
2013-12-06 12:04:52 +01:00
|
|
|
.WAIT \
|
|
|
|
.WAIT \
|
|
|
|
.WAIT \
|
2015-09-11 00:02:37 +02:00
|
|
|
.WAIT installboot \
|
2014-03-16 14:39:21 +01:00
|
|
|
pwd_mkdb stat strfile zic
|
2013-12-06 12:04:52 +01:00
|
|
|
.endif
|
|
|
|
.if defined(__MINIX)
|
|
|
|
SUBDIR += \
|
|
|
|
mkfs.mfs \
|
|
|
|
partition \
|
|
|
|
toproto \
|
|
|
|
writeisofs
|
|
|
|
.else
|
|
|
|
SUBDIR+= .WAIT config
|
|
|
|
.endif # defined(__MINIX)
|
2012-06-06 16:46:00 +02:00
|
|
|
|
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 ${MKLLVM} != "no"
|
|
|
|
SUBDIR+= \
|
|
|
|
llvm .WAIT \
|
|
|
|
llvm-lib/libLLVMSupport llvm-lib/libLLVMTableGen .WAIT \
|
2013-12-06 12:04:52 +01:00
|
|
|
llvm-tblgen llvm-clang-tblgen .WAIT \
|
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
|
|
|
llvm-include .WAIT \
|
|
|
|
llvm-lib .WAIT \
|
|
|
|
llvm-clang
|
2013-12-06 12:04:52 +01:00
|
|
|
.if ${MKLLD} != "no"
|
|
|
|
SUBDIR+= llvm-lld
|
|
|
|
.endif
|
|
|
|
.if ${MKMCLINKER} != "no"
|
|
|
|
SUBDIR+= llvm-mcld
|
|
|
|
.endif
|
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
|
2012-06-06 16:46:00 +02:00
|
|
|
|
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 ${MKMAN} != "no" || ${MKDOC} != "no" || ${MKHTML} != "no"
|
|
|
|
. if ${MKGROFF} != "no"
|
|
|
|
SUBDIR+= groff
|
|
|
|
. endif
|
|
|
|
SUBDIR+= mandoc
|
|
|
|
.endif
|
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
.if ${TOOLS_BUILDRUMP} == "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
|
|
|
.if ${MKMAINTAINERTOOLS:Uno} != "no"
|
|
|
|
SUBDIR+= autoconf .WAIT gettext
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if ${USE_PIGZGZIP} != "no"
|
|
|
|
SUBDIR+= pigz
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if ${MACHINE} == "hp700"
|
|
|
|
SUBDIR+= hp700-mkboot
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if ${MACHINE} == "ibmnws"
|
|
|
|
SUBDIR+= ibmnws-ncdcs
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if ${MACHINE} == "macppc"
|
|
|
|
SUBDIR+= macppc-fixcoff
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if (${MACHINE} == "prep" || ${MACHINE} == "rs6000" || ${MACHINE} == "bebox")
|
|
|
|
SUBDIR+= powerpc-mkbootimage
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if ${MACHINE_ARCH} == "m68k"
|
|
|
|
SUBDIR+= m68k-elf2aout
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if (${MACHINE_ARCH} == "mipsel" || ${MACHINE_ARCH} == "mipseb" || \
|
|
|
|
${MACHINE_ARCH} == "mips64el" || ${MACHINE_ARCH} == "mips64eb")
|
|
|
|
SUBDIR+= mips-elf2ecoff
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if (${MACHINE} == "sgimips")
|
|
|
|
SUBDIR+= sgivol
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if ${MACHINE} == "acorn32"
|
|
|
|
SUBDIR+= sparkcrc
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if (${MACHINE_ARCH} == "sparc" || ${MACHINE_ARCH} == "sparc64")
|
|
|
|
SUBDIR+= fgen
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if ${MACHINE} == "amiga"
|
|
|
|
SUBDIR+= amiga-elf2bb
|
|
|
|
SUBDIR+= amiga-txlt
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if ${MACHINE} == "hp300"
|
|
|
|
SUBDIR+= hp300-mkboot
|
|
|
|
.endif
|
|
|
|
|
2012-11-03 23:09:23 +01:00
|
|
|
.if !defined(__MINIX)
|
2013-12-06 12:04:52 +01:00
|
|
|
.if ${MACHINE} == "evbarm" \
|
|
|
|
&& ${MACHINE_CPU} == "arm" \
|
|
|
|
&& ${TARGET_ENDIANNESS} == "1234"
|
|
|
|
SUBDIR+= elftosb
|
|
|
|
.endif
|
|
|
|
|
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 ${MACHINE} == "evbarm" || ${MACHINE} == "evbmips" || \
|
|
|
|
${MACHINE} == "evbppc" || ${MACHINE} == "sandpoint"
|
|
|
|
SUBDIR+= mkubootimage
|
|
|
|
.endif
|
2012-11-03 23:09:23 +01:00
|
|
|
.endif # !defined(__MINIX)
|
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
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
.endif # TOOLCHAIN_BUILDRUMP
|
|
|
|
|
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
|
|
|
check_MKTOOLS: .PHONY .NOTMAIN
|
|
|
|
.if ${MKTOOLS:Uyes} == "no"
|
|
|
|
@echo '*** WARNING: "MKTOOLS" is set to "no"; this will prevent building and'
|
|
|
|
@echo '*** updating your host toolchain. This should be used only as a'
|
|
|
|
@echo '*** temporary workaround for toolchain problems, as it will result'
|
|
|
|
@echo '*** in version skew and build errors over time!'
|
|
|
|
.endif
|
2012-06-06 16:46:00 +02:00
|
|
|
|
|
|
|
.if ${MKTOOLS:Uyes} == "no" || ${USETOOLS} != "yes" # {
|
2013-12-06 12:04:52 +01:00
|
|
|
SUBDIR= # empty
|
2012-06-06 16:46:00 +02:00
|
|
|
realall realdepend install: check_MKTOOLS
|
|
|
|
.endif # }
|
|
|
|
|
|
|
|
.include <bsd.subdir.mk>
|
2013-12-06 12:04:52 +01:00
|
|
|
.include <bsd.buildinstall.mk>
|
2012-06-06 16:46:00 +02:00
|
|
|
.include <bsd.obj.mk>
|
|
|
|
|
|
|
|
.if !defined(PREVIOUSTOOLDIR)
|
|
|
|
. if exists(PREVIOUSTOOLDIR)
|
|
|
|
PREVIOUSTOOLDIR!= cat PREVIOUSTOOLDIR
|
|
|
|
. else
|
2013-12-06 12:04:52 +01:00
|
|
|
PREVIOUSTOOLDIR=
|
2012-06-06 16:46:00 +02:00
|
|
|
. endif
|
|
|
|
.endif
|
|
|
|
|
|
|
|
CLEANFILES+= PREVIOUSTOOLDIR
|
|
|
|
|
|
|
|
realall realdepend: .MAKE
|
|
|
|
.if !empty(PREVIOUSTOOLDIR) && "${PREVIOUSTOOLDIR}" != "${TOOLDIR}"
|
|
|
|
@echo "*** WARNING: TOOLDIR has moved?"
|
|
|
|
@echo "*** PREVIOUSTOOLDIR '${PREVIOUSTOOLDIR}'"
|
|
|
|
@echo "*** != TOOLDIR '${TOOLDIR}'"
|
|
|
|
@echo "*** Cleaning mis-matched tools"
|
|
|
|
rm -f PREVIOUSTOOLDIR
|
|
|
|
(cd ${.CURDIR} && ${MAKE} PREVIOUSTOOLDIR=${TOOLDIR} cleandir)
|
|
|
|
.endif
|
|
|
|
echo ${TOOLDIR} >PREVIOUSTOOLDIR
|
|
|
|
|
|
|
|
cleandir:
|
|
|
|
rm -f ${CLEANFILES}
|