freebsd-dev/libexec/tftp-proxy/Makefile

#	$FreeBSD$

.PATH:	${SRCTOP}/contrib/pf/tftp-proxy

PROG=	tftp-proxy
SRCS=	tftp-proxy.c filter.c
MAN=	tftp-proxy.8

WARNS?=	3

.include <bsd.prog.mk>
Link pf 4.1 to the build: - move ftp-proxy from libexec to usr.sbin - add tftp-proxy - new altq mtag link Approved by: re (kensmith) 2007-07-03 12:46:08 +00:00			`# $FreeBSD$`

libexec: normalize paths using SRCTOP-relative paths or :H when possible This simplifies make logic/output MFC after: 1 month Sponsored by: Dell EMC Isilon 2017-03-04 11:28:03 +00:00			`.PATH: ${SRCTOP}/contrib/pf/tftp-proxy`
Link pf 4.1 to the build: - move ftp-proxy from libexec to usr.sbin - add tftp-proxy - new altq mtag link Approved by: re (kensmith) 2007-07-03 12:46:08 +00:00
			`PROG= tftp-proxy`
			`SRCS= tftp-proxy.c filter.c`
			`MAN= tftp-proxy.8`

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 09:50:19 +00:00			`WARNS?= 3`

Link pf 4.1 to the build: - move ftp-proxy from libexec to usr.sbin - add tftp-proxy - new altq mtag link Approved by: re (kensmith) 2007-07-03 12:46:08 +00:00			`.include <bsd.prog.mk>`