opnsense-src/libexec/bootpd/Makefile

# bootpd/Makefile
# $FreeBSD$

PROG=	bootpd
CFLAGS+= -DETC_ETHERS
CFLAGS+= -DSYSLOG -DDEBUG -DVEND_CMU

WARNS?=	2

SUBDIR= bootpgw tools

SRCS=	bootpd.c dovend.c readfile.c hash.c dumptab.c \
	 lookup.c getif.c hwaddr.c report.c tzone.c rtmsg.c

MAN=	bootptab.5 bootpd.8
MLINKS=	bootpd.8 bootpgw.8

.include <bsd.prog.mk>
Rearrange bootpd 1994-09-30 01:45:07 -04:00			`# bootpd/Makefile`
$Id$ -> $FreeBSD$ 1999-08-27 20:22:10 -04:00			`# $FreeBSD$`
Rearrange bootpd 1994-09-30 01:45:07 -04:00
			`PROG= bootpd`
Uncomment 'CFLAGS+=ETC_ETHERS' -- we have support for this as of 2.0.5. 1995-07-25 19:38:40 -04:00			`CFLAGS+= -DETC_ETHERS`
Rearrange bootpd 1994-09-30 01:45:07 -04:00			`CFLAGS+= -DSYSLOG -DDEBUG -DVEND_CMU`

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?= 2`

Fix conflicts from 2.4.3 merge 1996-01-22 20:58:00 -05:00			`SUBDIR= bootpgw tools`
Rearrange bootpd 1994-09-30 01:45:07 -04:00
			`SRCS= bootpd.c dovend.c readfile.c hash.c dumptab.c \`
			`lookup.c getif.c hwaddr.c report.c tzone.c rtmsg.c`

- Backout botched attempt to intoduce MANSECT feature. - MAN[1-9] -> MAN. 2001-03-26 09:22:12 -05:00			`MAN= bootptab.5 bootpd.8`
Add some missing manual page links. 1996-02-02 12:48:46 -05:00			`MLINKS= bootpd.8 bootpgw.8`
Rearrange bootpd 1994-09-30 01:45:07 -04:00
			`.include <bsd.prog.mk>`