2013-12-06 12:04:52 +01:00
|
|
|
# $NetBSD: Makefile,v 1.209 2013/11/28 12:08:56 mrg 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
|
|
|
# from: @(#)Makefile 5.25.1.1 (Berkeley) 5/7/91
|
|
|
|
|
|
2010-06-25 20:29:09 +02:00
|
|
|
.include <bsd.own.mk>
|
2006-01-16 16:47:30 +01: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
|
|
|
SUBDIR= csu .WAIT
|
|
|
|
|
|
|
|
|
|
.if (${MKGCC} != "no")
|
|
|
|
|
. if ${HAVE_GCC} == 4
|
|
|
|
|
. if (${USE_COMPILERCRTSTUFF} == "yes")
|
|
|
|
|
SUBDIR+= ../gnu/lib/crtstuff4 .WAIT
|
|
|
|
|
. endif
|
|
|
|
|
SUBDIR+= ../gnu/lib/libgcc4 .WAIT
|
|
|
|
|
. else
|
|
|
|
|
. if (${USE_COMPILERCRTSTUFF} == "yes")
|
|
|
|
|
SUBDIR+= ../external/gpl3/gcc/lib/crtstuff .WAIT
|
|
|
|
|
. endif
|
|
|
|
|
SUBDIR+= ../external/gpl3/gcc/lib/libgcc .WAIT
|
|
|
|
|
. endif
|
|
|
|
|
.endif
|
|
|
|
|
|
2014-07-28 21:19:37 +02:00
|
|
|
.if defined(__MINIX)
|
2014-01-14 13:48:43 +01:00
|
|
|
#LSC MINIX libc depends on
|
|
|
|
|
# - libmthread because of sys/lib/libunwind
|
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
|
|
|
SUBDIR+= .WAIT
|
|
|
|
|
|
2014-07-28 21:19:37 +02:00
|
|
|
SUBDIR+= ../minix/lib/libsys
|
|
|
|
|
SUBDIR+= ../minix/lib/libmthread
|
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
|
|
|
SUBDIR+= .WAIT
|
2014-07-28 21:19:37 +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
|
|
|
SUBDIR+= libc
|
|
|
|
|
SUBDIR+= .WAIT
|
|
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
.if defined(__MINIX)
|
2014-07-28 21:19:37 +02:00
|
|
|
SUBDIR+= ../minix/lib/libasyn \
|
|
|
|
|
../minix/lib/libaudiodriver \
|
|
|
|
|
../minix/lib/libbdev \
|
|
|
|
|
../minix/lib/libblockdriver \
|
|
|
|
|
../minix/lib/libchardriver \
|
|
|
|
|
../minix/lib/libddekit \
|
|
|
|
|
../minix/lib/libdevman \
|
|
|
|
|
../minix/lib/libexec \
|
2014-08-24 11:27:54 +02:00
|
|
|
../minix/lib/libfsdriver \
|
2014-07-28 21:19:37 +02:00
|
|
|
../minix/lib/libinputdriver \
|
|
|
|
|
../minix/lib/libminc \
|
|
|
|
|
../minix/lib/libminixfs \
|
|
|
|
|
../minix/lib/libnetdriver \
|
|
|
|
|
../minix/lib/libsffs \
|
|
|
|
|
../minix/lib/libtimers \
|
|
|
|
|
../minix/lib/libusb \
|
|
|
|
|
../minix/lib/libvtreefs
|
2013-12-06 12:04:52 +01:00
|
|
|
|
2014-07-17 14:32:35 +02:00
|
|
|
.if (${HAVE_LIBGCC} == "no")
|
2014-07-28 21:19:37 +02:00
|
|
|
SUBDIR+= ../minix/lib/libgcc_s_empty
|
2014-07-17 14:32:35 +02:00
|
|
|
.endif
|
|
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
.if (${MKLWIP} == "yes")
|
2014-07-28 21:19:37 +02:00
|
|
|
SUBDIR+= ../minix/lib/liblwip \
|
|
|
|
|
../minix/lib/libnetsock
|
2013-12-06 12:04:52 +01:00
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
.if (${MACHINE_ARCH} == "i386")
|
2014-07-28 21:19:37 +02:00
|
|
|
SUBDIR+= ../minix/lib/libhgfs \
|
|
|
|
|
../minix/lib/libvassert \
|
|
|
|
|
../minix/lib/libvboxfs \
|
|
|
|
|
../minix/lib/libvirtio
|
2013-12-06 12:04:52 +01:00
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
.if (${MACHINE_ARCH} == "earm")
|
2014-07-28 21:19:37 +02:00
|
|
|
SUBDIR+= ../minix/lib/libclkconf \
|
|
|
|
|
../minix/lib/libgpio \
|
|
|
|
|
../minix/lib/libi2cdriver
|
2013-12-06 12:04:52 +01:00
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
.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
|
|
|
#
|
|
|
|
|
# The SUBDIRs above are included here for completeness but should be built
|
|
|
|
|
# and installed prior to make(dependall) in this file, as libraries listed
|
|
|
|
|
# below will depend on versions from DESTDIR only.
|
|
|
|
|
#
|
2006-01-16 16:47:30 +01: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
|
|
|
#SUBDIR+= i18n_module
|
2012-02-17 00:06:42 +01:00
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
SUBDIR+= \
|
|
|
|
|
libbz2 \
|
|
|
|
|
libcrypt \
|
|
|
|
|
libm \
|
2014-10-15 09:51:53 +02:00
|
|
|
libpci libprop \
|
2013-12-06 12:04:52 +01:00
|
|
|
libpuffs librmt \
|
|
|
|
|
libterminfo \
|
|
|
|
|
libutil libz
|
2013-02-06 11:43:02 +01:00
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
.if !defined(BSD_MK_COMPAT_FILE)
|
|
|
|
|
#SUBDIR+= libkern
|
2013-02-06 11:43:02 +01:00
|
|
|
.endif
|
2013-01-13 17:20:11 +01:00
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
.if (${MACHINE_CPU} == "arm")
|
|
|
|
|
LIBC_MACHINE_ARCH?=${MACHINE_ARCH}
|
|
|
|
|
.if empty(LIBC_MACHINE_ARCH:M*hf*)
|
2014-12-11 15:00:57 +01:00
|
|
|
.if !defined(__MINIX)
|
2013-12-06 12:04:52 +01:00
|
|
|
SUBDIR+= libc_vfp
|
2013-01-13 17:20:11 +01:00
|
|
|
.endif
|
2013-02-06 15:46:21 +01:00
|
|
|
.endif
|
2014-12-11 15:00:57 +01:00
|
|
|
.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 (${MKRUMP} != "no")
|
|
|
|
|
SUBDIR+= librumpclient
|
|
|
|
|
.endif
|
|
|
|
|
.if (${MKSKEY} != "no")
|
|
|
|
|
SUBDIR+= libskey
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
.if (${MKMDNS} != "no")
|
|
|
|
|
SUBDIR+= ../external/apache2/mDNSResponder/lib
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
#SUBDIR+= ../external/bsd/am-utils/lib
|
2012-03-31 02:28:03 +02:00
|
|
|
|
2012-06-06 16:10:32 +02:00
|
|
|
SUBDIR+= ../external/bsd/flex/lib
|
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
|
|
|
#SUBDIR+= ../external/bsd/tre/lib
|
2013-12-06 12:04:52 +01:00
|
|
|
SUBDIR+= ../external/bsd/libelf/lib
|
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
|
|
|
#SUBDIR+= ../external/bsd/liblzf/lib
|
|
|
|
|
#SUBDIR+= ../external/bsd/libpcap/lib
|
|
|
|
|
|
2013-12-14 04:48:37 +01:00
|
|
|
SUBDIR+= ../external/mit/expat/lib
|
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-02-26 09:24:42 +01:00
|
|
|
SUBDIR+= ../external/public-domain/sqlite/lib
|
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
|
|
|
SUBDIR+= ../external/public-domain/xz/lib
|
|
|
|
|
|
|
|
|
|
#SUBDIR+= ../gnu/lib/libmalloc
|
|
|
|
|
|
|
|
|
|
.if (${MKGCC} != "no")
|
|
|
|
|
. if ${HAVE_GCC} == 4
|
|
|
|
|
#SUBDIR+= ../gnu/lib/libobjc4
|
|
|
|
|
. else
|
2013-12-06 16:46:30 +01:00
|
|
|
. if !defined(__MINIX) || ${MKLIBSTDCXX} == "yes"
|
2013-12-06 12:04:52 +01:00
|
|
|
SUBDIR+= ../external/gpl3/gcc/lib/libobjc
|
|
|
|
|
SUBDIR+= ../external/gpl3/gcc/lib/libgomp
|
2013-12-06 16:46:30 +01:00
|
|
|
. endif # !defined(__MINIX) || ${MKLIBSTDCXX} == "yes"
|
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 16:46:30 +01:00
|
|
|
. if ${HAVE_GCC} >= 45 && !defined(MLIBDIR)
|
|
|
|
|
. if !defined(__MINIX) || ${MKLIBSTDCXX} == "yes"
|
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
|
|
|
# Should probably move GMP, MPFR and MPC builds into the GCC >= 4.5
|
|
|
|
|
# specific build area, but we get better parallelism this way.
|
|
|
|
|
SUBDIR+= ../external/lgpl3/gmp/lib/libgmp
|
|
|
|
|
SUBDIR+= ../external/lgpl3/mpfr/lib/libmpfr
|
2013-12-06 12:04:52 +01:00
|
|
|
SUBDIR+= ../external/lgpl3/mpc/lib/libmpc
|
2013-12-06 16:46:30 +01:00
|
|
|
. endif # !defined(__MINIX) || ${MKLIBSTDCXX} == "yes"
|
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
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Libraries that depend upon any listed previously
|
|
|
|
|
# (and those that depend upon these [and ...])
|
|
|
|
|
#
|
|
|
|
|
#==================== 1st library dependency barrier ====================
|
|
|
|
|
SUBDIR+= .WAIT
|
|
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
.if (${MKCRYPTO} != "no")
|
|
|
|
|
SUBDIR+= ../crypto/external/bsd/netpgp/libmj
|
|
|
|
|
SUBDIR+= ../crypto/external/bsd/netpgp/lib/verify # depends on libz
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
#SUBDIR+= ../external/bsd/libdwarf/lib # depends on libelf
|
|
|
|
|
SUBDIR+= ../external/mit/lua/lib # depends on libm
|
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
|
|
|
SUBDIR+= libcurses # depends on libterminfo
|
|
|
|
|
#SUBDIR+= libdm # depends on libprop
|
2013-01-22 12:03:53 +01:00
|
|
|
SUBDIR+= libedit # depends on libterminfo
|
2013-12-06 12:04:52 +01:00
|
|
|
SUBDIR+= libexecinfo # depends on libelf
|
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
|
|
|
#SUBDIR+= libppath # depends on libprop
|
|
|
|
|
#SUBDIR+= libperfuse # depends on libpuffs
|
|
|
|
|
#SUBDIR+= libquota # depends on libprop and librpcsvc
|
|
|
|
|
SUBDIR+= librefuse # depends on libpuffs
|
2013-12-06 12:04:52 +01:00
|
|
|
#SUBDIR+= libisns # depends on libpthread
|
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 (${MKRUMP} != "no")
|
|
|
|
|
SUBDIR+= librumpuser # depends on libpthread
|
|
|
|
|
SUBDIR+= librumphijack # depends on librumpclient and libpthread
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
.if (${MKNPF} != "no")
|
|
|
|
|
SUBDIR+= libnpf # depends on libprop
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
.if (${MKCRYPTO} != "no")
|
|
|
|
|
SUBDIR+= ../crypto/external/bsd/openssl/lib # depends on libcrypt
|
|
|
|
|
.endif
|
|
|
|
|
|
2013-04-10 11:08:42 +02:00
|
|
|
SUBDIR+= ../external/bsd/file/lib # depends on libz
|
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 (${MKISCSI} != "no")
|
|
|
|
|
SUBDIR+= ../external/bsd/iscsi/lib # depends on libpthread
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
SUBDIR+= ../external/bsd/libarchive/lib # depends on libxz
|
|
|
|
|
|
|
|
|
|
.if (${MKLVM} != "no")
|
|
|
|
|
SUBDIR+= ../external/gpl2/lvm2/lib # depends on libprop
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
.if (${MKBINUTILS} != "no")
|
|
|
|
|
SUBDIR+= ../external/gpl3/binutils/lib # libbfd depends on libz
|
|
|
|
|
.endif
|
|
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
.if (${MKLIBCXX} != "no")
|
|
|
|
|
SUBDIR+= ../external/bsd/libc++
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
.if (${MKGCC} != "no" && ${MKCXX} != "no" && ${MKLIBSTDCXX} != "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 ${HAVE_GCC} == 4
|
|
|
|
|
SUBDIR+= ../gnu/lib/libstdc++-v3_4 # depends on libm
|
|
|
|
|
SUBDIR+= ../gnu/lib/libsupc++4
|
|
|
|
|
. else
|
2013-02-26 09:24:42 +01:00
|
|
|
SUBDIR+= ../external/gpl3/gcc/lib/libstdc++-v3
|
|
|
|
|
SUBDIR+= ../external/gpl3/gcc/lib/libsupc++
|
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
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
#==================== 2nd library dependency barrier ====================
|
|
|
|
|
SUBDIR+= .WAIT
|
|
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
.if (${MKNPF} != "no")
|
|
|
|
|
SUBDIR+= npf # depends on libnpf
|
|
|
|
|
.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 (${MKATF} != "no")
|
|
|
|
|
SUBDIR+= ../external/bsd/atf/lib # depends on libstdc++
|
|
|
|
|
.endif
|
|
|
|
|
|
2013-02-26 09:24:42 +01:00
|
|
|
.if (${MKKYUA} != "no")
|
|
|
|
|
SUBDIR+= ../external/bsd/lutok/lib # depends on lua and libstdc++
|
|
|
|
|
.endif
|
|
|
|
|
|
2013-11-12 13:56:07 +01:00
|
|
|
SUBDIR+= libform # depends on libcurses
|
2013-11-12 13:39:59 +01:00
|
|
|
SUBDIR+= libmenu # depends on libcurses
|
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
|
|
|
#SUBDIR+= libradius # depends on libcrypto if (${MKCRYPTO} != "no")
|
|
|
|
|
.if (${MKRUMP} != "no")
|
|
|
|
|
SUBDIR+= librump # depends on librumpuser
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
.if (${MKKERBEROS} != "no")
|
|
|
|
|
SUBDIR+= ../crypto/external/bsd/heimdal/lib # depends on libcrypto
|
|
|
|
|
# libedit, libterminfo,
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
.if (${MKCRYPTO} != "no")
|
2015-10-07 02:45:38 +02:00
|
|
|
#SUBDIR+= ../crypto/external/bsd/openssh/lib # depends on libcrypto, libz
|
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
|
|
|
SUBDIR+= ../crypto/external/bsd/netpgp/lib # depends on libcrypto, ...
|
|
|
|
|
.endif
|
|
|
|
|
|
2014-10-01 17:39:05 +02:00
|
|
|
SUBDIR+= ../external/bsd/libevent/lib # depends on libcrypto
|
2015-09-20 01:46:56 +02:00
|
|
|
SUBDIR+= ../external/bsd/fetch/lib # depends on libssl
|
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 (${MKLDAP} != "no")
|
|
|
|
|
SUBDIR+= ../external/bsd/openldap/lib # depends on libcrypto, ...
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
#==================== 3rd library dependency barrier ====================
|
|
|
|
|
SUBDIR+= .WAIT
|
|
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
#SUBDIR+= ../external/bsd/bind/lib # depends on heimdal, libcrypto
|
|
|
|
|
|
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 (${MKRUMP} != "no")
|
|
|
|
|
SUBDIR+= librumpdev # depends on librump
|
|
|
|
|
SUBDIR+= librumpnet # depends on librump
|
|
|
|
|
SUBDIR+= librumpvfs # depends on librump
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
.if (${MKPAM} != "no")
|
|
|
|
|
SUBDIR+= libpam # depends on heimdal
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
.if (${MKCRYPTO} != "no")
|
|
|
|
|
SUBDIR+= ../crypto/external/bsd/libsaslc # depends on heimdal, openssl
|
|
|
|
|
.endif
|
|
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
.if ${MKSLJIT} != "no"
|
|
|
|
|
SUBDIR+= ../external/bsd/sljit/lib
|
|
|
|
|
SUBDIR+= .WAIT
|
|
|
|
|
SUBDIR+= libbpfjit
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
SUBDIR+= ../external/bsd/mdocml/lib
|
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 (${MKRUMP} != "no")
|
|
|
|
|
#==================== 4th library dependency barrier ====================
|
|
|
|
|
SUBDIR+= .WAIT
|
|
|
|
|
|
|
|
|
|
SUBDIR+= libukfs # depends on librumpvfs, librump
|
|
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
.if (${MKTPM} != "no")
|
|
|
|
|
SUBDIR+= ../crypto/external/cpl/trousers/lib
|
|
|
|
|
.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
|
|
|
#==================== 5th library dependency barrier ====================
|
|
|
|
|
SUBDIR+= .WAIT
|
|
|
|
|
|
|
|
|
|
SUBDIR+= libp2k # depends on libukfs, librumpvfs, libpuffs
|
|
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
.if (${MKTPM} != "no")
|
|
|
|
|
SUBDIR+= ../crypto/external/cpl/tpm-tools/lib # depends on trousers
|
|
|
|
|
.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(BSD_MK_COMPAT_FILE)
|
|
|
|
|
SUBDIR+= ../sys/rump/dev/lib
|
|
|
|
|
SUBDIR+= ../sys/rump/fs/lib
|
|
|
|
|
SUBDIR+= ../sys/rump/kern/lib
|
|
|
|
|
SUBDIR+= ../sys/rump/net/lib
|
|
|
|
|
.endif
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
# Lua bindings come last, they might depend on anything
|
2013-12-06 12:04:52 +01:00
|
|
|
SUBDIR+= lua
|
2012-03-31 02:28:03 +02:00
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
.include <bsd.buildinstall.mk>
|
2010-06-25 20:29:09 +02:00
|
|
|
.include <bsd.subdir.mk>
|
