minix/tools/sed/Makefile

#	$NetBSD: Makefile,v 1.1 2006/06/18 05:16:41 gdamore Exp $

HOSTPROGNAME=	${_TOOL_PREFIX}sed
HOST_SRCDIR=	usr.bin/sed

.ifdef __MINIX
SYMLINKS=	# defined so usr.bin/sed/Makefile does not set it
.endif

.include "${.CURDIR}/../Makefile.host"
Import NetBSD tools and build.sh This commit finalizes support for cross compilation. The tools directory are all links to the actual tools and are built on the host system to build Minix. build.sh is the work horse that takes care of all environment settings. It's slightly adjusted for Minix. The /usr/src/Makefile has additional targets needed for cross compilation. 2012-06-06 16:46:00 +02:00			`# $NetBSD: Makefile,v 1.1 2006/06/18 05:16:41 gdamore Exp $`

			`HOSTPROGNAME= ${_TOOL_PREFIX}sed`
			`HOST_SRCDIR= usr.bin/sed`
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
			`.ifdef __MINIX`
sed: unbreak crosscompilation 2012-06-21 16:07:59 +02:00			`SYMLINKS= # defined so usr.bin/sed/Makefile does not set it`
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`
Import NetBSD tools and build.sh This commit finalizes support for cross compilation. The tools directory are all links to the actual tools and are built on the host system to build Minix. build.sh is the work horse that takes care of all environment settings. It's slightly adjusted for Minix. The /usr/src/Makefile has additional targets needed for cross compilation. 2012-06-06 16:46:00 +02:00
			`.include "${.CURDIR}/../Makefile.host"`