NetBSD/usr.bin/unifdef/Makefile

#	$NetBSD: Makefile,v 1.7 2019/10/13 07:28:17 mrg Exp $
#	@(#)Makefile	8.1 (Berkeley) 6/6/93

PROG=	unifdef

SCRIPTS=unifdefall.sh

MLINKS=	unifdef.1 unifdefall.1

COPTS.unifdef.c+=	${GCC_NO_STRINGOP_TRUNCATION}

.include <bsd.prog.mk>
introduce some common variables for use in GCC warning disables: GCC_NO_FORMAT_TRUNCATION -Wno-format-truncation (GCC 7/8) GCC_NO_STRINGOP_TRUNCATION -Wno-stringop-truncation (GCC 8) GCC_NO_STRINGOP_OVERFLOW -Wno-stringop-overflow (GCC 8) GCC_NO_CAST_FUNCTION_TYPE -Wno-cast-function-type (GCC 8) use these to turn off warnings for most GCC-8 complaints. many of these are false positives, most of the real bugs are already commited, or are yet to come. we plan to introduce versions of (some?) of these that use the "-Wno-error=" form, which still displays the warnings but does not make it an error, and all of the above will be re-considered as either being "fix me" (warning still displayed) or "warning is wrong." 2019-10-13 10:28:04 +03:00			`# $NetBSD: Makefile,v 1.7 2019/10/13 07:28:17 mrg Exp $`
Merged with 4.4lite. Changed to conform to NetBSD's new RCS ID convention. 1994-12-07 03:33:47 +03:00			`# @(#)Makefile 8.1 (Berkeley) 6/6/93`
initial import of 386bsd-0.1 sources 1993-03-21 12:45:37 +03:00
			`PROG= unifdef`

Use SCRIPTS=unifdefall.sh instead of SCRIPTS=unifdefall, as the latter causes the .sh: rule in <sys.mk> to be used, which leaves unifdefall in the .OBJDIR unless a CLEANFILES rule is added. 2003-08-01 15:51:14 +04:00			`SCRIPTS=unifdefall.sh`
ANSI C support, from http://dotat.at/prog/misc/ PR 22303 2003-07-30 12:21:46 +04:00
unifdefall is available. 2003-07-30 12:24:11 +04:00			`MLINKS= unifdef.1 unifdefall.1`

introduce some common variables for use in GCC warning disables: GCC_NO_FORMAT_TRUNCATION -Wno-format-truncation (GCC 7/8) GCC_NO_STRINGOP_TRUNCATION -Wno-stringop-truncation (GCC 8) GCC_NO_STRINGOP_OVERFLOW -Wno-stringop-overflow (GCC 8) GCC_NO_CAST_FUNCTION_TYPE -Wno-cast-function-type (GCC 8) use these to turn off warnings for most GCC-8 complaints. many of these are false positives, most of the real bugs are already commited, or are yet to come. we plan to introduce versions of (some?) of these that use the "-Wno-error=" form, which still displays the warnings but does not make it an error, and all of the above will be re-considered as either being "fix me" (warning still displayed) or "warning is wrong." 2019-10-13 10:28:04 +03:00			`COPTS.unifdef.c+= ${GCC_NO_STRINGOP_TRUNCATION}`

initial import of 386bsd-0.1 sources 1993-03-21 12:45:37 +03:00			`.include <bsd.prog.mk>`