minix/usr.bin/mkdep/Makefile

#	$NetBSD: Makefile,v 1.17 2009/04/12 14:23:30 lukem Exp $
#	@(#)Makefile	8.1 (Berkeley) 6/6/93

#CFLAGS+=-g
MAN=	mkdep.1
PROG=	mkdep
SRCS=	mkdep.c findcc.c

# LSC Until it compiles cleanly...
NOGCCERROR:=yes

.include <bsd.prog.mk>
Import NetBSD mkdep 2011-07-22 17:28:27 +02:00			`# $NetBSD: Makefile,v 1.17 2009/04/12 14:23:30 lukem Exp $`
			`# @(#)Makefile 8.1 (Berkeley) 6/6/93`

			`#CFLAGS+=-g`
			`MAN= mkdep.1`
			`PROG= mkdep`
			`SRCS= mkdep.c findcc.c`

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			`# LSC Until it compiles cleanly...`
			`NOGCCERROR:=yes`

Import NetBSD mkdep 2011-07-22 17:28:27 +02:00			`.include <bsd.prog.mk>`