opnsense-src/libexec/rbootd/Makefile

#	from: @(#)Makefile	8.1 (Berkeley) 6/4/93
# $FreeBSD$

PROG=	rbootd
SRCS=	bpf.c conf.c parseconf.c rbootd.c rmpproto.c utils.c
MAN=	rbootd.8

WARNS?=	1
WFORMAT=0

.include <bsd.prog.mk>
Merge conflicts and make this compile -Wall clean. 1997-06-29 15:00:29 -04:00			`# from: @(#)Makefile 8.1 (Berkeley) 6/4/93`
$Id$ -> $FreeBSD$ 1999-08-27 20:22:10 -04:00			`# $FreeBSD$`
BSD 4.4 Lite Libexec Sources 1994-05-27 08:39:25 -04:00
			`PROG= rbootd`
			`SRCS= bpf.c conf.c parseconf.c rbootd.c rmpproto.c utils.c`
- Backout botched attempt to intoduce MANSECT feature. - MAN[1-9] -> MAN. 2001-03-26 09:22:12 -05:00			`MAN= rbootd.8`
BSD 4.4 Lite Libexec Sources 1994-05-27 08:39:25 -04:00
Make WARNS=6 the default for libexec/. Just like bin/ and sbin/, I think setting WARNS to the highest value possible will make it more attractive for people to fix warnings. - The WARNS variable is set in the Makefile in the directory of the application itself, making it more likely that it will be removed out of curiosity to see what happens. - New applications will most likely build with WARNS=6 out of the box, because the author would more likely fix the warnings during development than lower WARNS. Unfortunately almost all apps in libexec require a lowered value of WARNS. 2010-01-02 04:50:19 -05:00			`WARNS?= 1`
Lock down with WFORMAT?=1, with overrides in the subdirectories which are not yet warning-clean. Tested on i386 and alpha. 2002-02-03 21:33:51 -05:00			`WFORMAT=0`

BSD 4.4 Lite Libexec Sources 1994-05-27 08:39:25 -04:00			`.include <bsd.prog.mk>`