2013-01-22 12:03:53 +01:00
|
|
|
# $NetBSD: Makefile,v 1.189 2012/09/16 13:47:41 rmind 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
|
|
|
|
|
|
|
|
#LSC MINIX libc depends on libminlib because of minix/malloc-debug.c
|
|
|
|
SUBDIR+= libminlib
|
|
|
|
SUBDIR+= .WAIT
|
|
|
|
|
|
|
|
SUBDIR+= libsys
|
|
|
|
SUBDIR+= .WAIT
|
|
|
|
|
|
|
|
SUBDIR+= libc
|
|
|
|
SUBDIR+= .WAIT
|
|
|
|
|
|
|
|
#
|
|
|
|
# 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
|
|
|
|
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+= libcompat_minix libblockdriver libchardriver \
|
2013-01-22 12:03:53 +01:00
|
|
|
libnetdriver libm libtimers libutil \
|
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
|
|
|
libz libfetch libvtreefs libaudiodriver libmthread \
|
|
|
|
libexec libdevman libusb libasyn librmt \
|
|
|
|
libddekit libminixfs libbdev libelf libminc libcrypt libterminfo \
|
2013-01-13 17:20:11 +01:00
|
|
|
libutil libbz2 libprop \
|
Input infrastructure, INPUT server, PCKBD driver
This commit separates the low-level keyboard driver from TTY, putting
it in a separate driver (PCKBD). The commit also separates management
of raw input devices from TTY, and puts it in a separate server
(INPUT). All keyboard and mouse input from hardware is sent by drivers
to the INPUT server, which either sends it to a process that has
opened a raw input device, or otherwise forwards it to TTY for
standard processing.
Design by Dirk Vogt. Prototype by Uli Kastlunger.
Additional changes made to the prototype:
- the event communication is now based on USB HID codes; all input
drivers have to use USB codes to describe events;
- all TTY keymaps have been converted to USB format, with the effect
that a single keymap covers all keys; there is no (static) escaped
keymap anymore;
- further keymap tweaks now allow remapping of literally all keys;
- input device renumbering and protocol rewrite;
- INPUT server rewrite, with added support for cancel and select;
- PCKBD reimplementation, including PC/AT-to-USB translation;
- support for manipulating keyboard LEDs has been added;
- keyboard and mouse multiplexer devices have been added to INPUT,
primarily so that an X server need only open two devices;
- a new "libinputdriver" library abstracts away protocol details from
input drivers, and should be used by all future input drivers;
- both INPUT and PCKBD can be restarted;
- TTY is now scheduled by KERNEL, so that it won't be punished for
running a lot; without this, simply running "yes" on the console
kills the system;
- the KIOCBELL IOCTL has been moved to /dev/console;
- support for the SCANCODES termios setting has been removed;
- obsolete keymap compression has been removed;
- the obsolete Olivetti M24 keymap has been removed.
Change-Id: I3a672fb8c4fd566734e4b46d3994b4b7fc96d578
2013-09-28 14:46:21 +02:00
|
|
|
libpuffs libsffs libinputdriver
|
2013-02-06 11:43:02 +01:00
|
|
|
|
|
|
|
.if (${MKLWIP} == "yes")
|
|
|
|
SUBDIR += liblwip libnetsock
|
|
|
|
.endif
|
2013-01-13 17:20:11 +01:00
|
|
|
|
2013-02-06 15:46:21 +01:00
|
|
|
.if (${MACHINE_ARCH} == "i386")
|
2012-12-15 13:47:37 +01:00
|
|
|
SUBDIR += libvassert libhgfs libvboxfs libvirtio
|
2013-01-13 17:20:11 +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
|
|
|
|
2013-02-06 15:46:21 +01:00
|
|
|
.if (${MACHINE_ARCH} == "earm")
|
2013-08-28 06:43:45 +02:00
|
|
|
SUBDIR += libclkconf libgpio libi2cdriver
|
2013-02-06 15:46:21 +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 (${MKCRYPTO} != "no")
|
|
|
|
SUBDIR+= ../crypto/external/bsd/netpgp/libmj
|
|
|
|
.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
|
|
|
|
#SUBDIR+= ../external/bsd/libdwarf/lib
|
|
|
|
#SUBDIR+= ../external/bsd/libelf/lib
|
|
|
|
#SUBDIR+= ../external/bsd/libevent/lib
|
|
|
|
#SUBDIR+= ../external/bsd/liblzf/lib
|
|
|
|
#SUBDIR+= ../external/bsd/libpcap/lib
|
|
|
|
|
2013-02-26 09:24:42 +01:00
|
|
|
SUBDIR+= ../external/mit/lua/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/mit/expat/lib
|
|
|
|
|
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
|
|
|
|
#SUBDIR+= ../external/gpl3/gcc/lib/libobjc
|
|
|
|
#SUBDIR+= ../external/gpl3/gcc/lib/libgomp
|
|
|
|
. endif
|
2013-04-24 18:57:59 +02:00
|
|
|
# LSC: Replaced __MINIX test with MKGCCCMDS, as we do not want gcc by default
|
|
|
|
# nor the libraries, but we still want toretain the possibility of
|
|
|
|
# installing GCC from the base system.
|
|
|
|
. if ${HAVE_GCC} >= 45 && !defined(MLIBDIR) && ${MKGCCCMDS} == "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
|
|
|
|
SUBDIR+= ../external/lgpl2/mpc/lib/libmpc
|
|
|
|
. endif
|
|
|
|
.endif
|
|
|
|
|
|
|
|
#
|
|
|
|
# Libraries that depend upon any listed previously
|
|
|
|
# (and those that depend upon these [and ...])
|
|
|
|
#
|
|
|
|
#==================== 1st library dependency barrier ====================
|
|
|
|
SUBDIR+= .WAIT
|
|
|
|
|
|
|
|
SUBDIR+= libcurses # depends on libterminfo
|
|
|
|
#SUBDIR+= libdm # depends on libprop
|
2013-01-22 12:03:53 +01:00
|
|
|
SUBDIR+= libedit # depends on libterminfo
|
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+= libexecinfo # depends on libelf
|
|
|
|
#SUBDIR+= libppath # depends on libprop
|
|
|
|
#SUBDIR+= libperfuse # depends on libpuffs
|
|
|
|
#SUBDIR+= libquota # depends on libprop and librpcsvc
|
|
|
|
SUBDIR+= librefuse # depends on libpuffs
|
|
|
|
.if (${MKRUMP} != "no")
|
|
|
|
SUBDIR+= librumpuser # depends on libpthread
|
|
|
|
SUBDIR+= librumphijack # depends on librumpclient and libpthread
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if (${MKNPF} != "no")
|
|
|
|
SUBDIR+= libnpf # depends on libprop
|
2013-01-22 12:03:53 +01:00
|
|
|
#SUBDIR+= npf
|
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
|
|
|
|
|
|
|
|
.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
|
|
|
|
|
|
|
|
.if (${MKGCC} != "no" && ${MKCXX} != "no")
|
2013-04-24 18:57:59 +02:00
|
|
|
.if (defined(__MINIX) && ${MKGCCCMDS} == "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
|
|
|
. 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
|
2013-04-24 18:57:59 +02:00
|
|
|
.endif # (defined(__MINIX) && ${MKGCCCMDS} == "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
|
|
|
|
|
|
|
|
#==================== 2nd library dependency barrier ====================
|
|
|
|
SUBDIR+= .WAIT
|
|
|
|
|
2013-02-26 09:24:42 +01:00
|
|
|
.if (defined(__MINIX) && ${MKGCCCMDS} == "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
|
|
|
.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
|
|
|
|
.endif # (defined(__MINIX) && ${MKGCCCMDS} == "yes")
|
|
|
|
|
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")
|
|
|
|
SUBDIR+= ../crypto/external/bsd/openssh/lib # depends on libcrypto, libz
|
|
|
|
SUBDIR+= ../crypto/external/bsd/netpgp/lib # depends on libcrypto, ...
|
|
|
|
.endif
|
|
|
|
|
|
|
|
#SUBDIR+= ../external/bsd/bind/lib # depends on libcrypto
|
|
|
|
#SUBDIR+= ../external/bsd/fetch/lib # depends on libssl
|
|
|
|
|
|
|
|
.if (${MKLDAP} != "no")
|
|
|
|
SUBDIR+= ../external/bsd/openldap/lib # depends on libcrypto, ...
|
|
|
|
.endif
|
|
|
|
|
|
|
|
#==================== 3rd library dependency barrier ====================
|
|
|
|
SUBDIR+= .WAIT
|
|
|
|
|
|
|
|
.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
|
|
|
|
|
|
|
|
#SUBDIR+= ../external/bsd/mdocml/lib
|
|
|
|
|
|
|
|
.if (${MKRUMP} != "no")
|
|
|
|
#==================== 4th library dependency barrier ====================
|
|
|
|
SUBDIR+= .WAIT
|
|
|
|
|
|
|
|
SUBDIR+= libukfs # depends on librumpvfs, librump
|
|
|
|
|
|
|
|
#==================== 5th library dependency barrier ====================
|
|
|
|
SUBDIR+= .WAIT
|
|
|
|
|
|
|
|
SUBDIR+= libp2k # depends on libukfs, librumpvfs, libpuffs
|
|
|
|
|
|
|
|
.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
|
|
|
|
#SUBDIR+= lua
|
|
|
|
|
|
|
|
#
|
|
|
|
# build_install logic for src/Makefile.
|
|
|
|
# Compute a list of subdirectories delimited by .WAIT.
|
|
|
|
# Run "make dependall && make install" for all subdirectories in a group
|
|
|
|
# concurrently, but wait after each group.
|
|
|
|
#
|
|
|
|
SUBDIR_GROUPS= 1
|
|
|
|
CUR_GROUP:= 1
|
|
|
|
.for dir in ${SUBDIR}
|
|
|
|
. if ${dir} == ".WAIT"
|
|
|
|
CUR_GROUP:= ${CUR_GROUP}1
|
|
|
|
SUBDIR_GROUPS:= ${SUBDIR_GROUPS} ${CUR_GROUP}
|
|
|
|
. else
|
|
|
|
SUBDIR_GROUP.${CUR_GROUP}+= ${dir}
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.endfor
|
|
|
|
|
|
|
|
build_install:
|
|
|
|
.for group in ${SUBDIR_GROUPS}
|
|
|
|
. if !empty(SUBDIR_GROUP.${group})
|
|
|
|
${MAKEDIRTARGET} . ${SUBDIR_GROUP.${group}:C/^/dependall-/}
|
|
|
|
${MAKEDIRTARGET} . ${SUBDIR_GROUP.${group}:C/^/install-/}
|
|
|
|
. endif
|
|
|
|
.endfor
|
2012-03-31 02:28:03 +02:00
|
|
|
|
2010-06-25 20:29:09 +02:00
|
|
|
.include <bsd.subdir.mk>
|