Do not hardcode warning and optimisation flags, otherwise the main options (i.e. DBG, CPPFLAGS) will not work as expected. You can still provide specific default by using DBG?=<value>. Doing so leaves the opportunity to override the setting from the commandline, while the default value from the build system is then ignored for that particular package. When crosscompiling, and using build.sh, adding -V DBG=<value> has this same effect as make DBG=<value>. Change-Id: Ic610e4d33b945acad64571e1431f1814291e2d84
21 lines
393 B
Makefile
21 lines
393 B
Makefile
# $NetBSD: Makefile,v 1.8 2007/11/05 13:41:52 pooka Exp $
|
|
|
|
USE_FORT?= no # data driven bugs?
|
|
|
|
LIB= refuse
|
|
LIBDPLIBS+= puffs ${.CURDIR}/../libpuffs
|
|
|
|
.ifdef DEBUG
|
|
FUSE_OPT_DEBUG_FLAGS= -DFUSE_OPT_DEBUG
|
|
.endif
|
|
|
|
CFLAGS+= ${FUSE_OPT_DEBUG_FLAGS}
|
|
SRCS= refuse.c refuse_opt.c
|
|
MAN= refuse.3
|
|
WARNS= 4
|
|
INCS= fuse.h fuse_opt.h
|
|
INCSDIR= /usr/include
|
|
|
|
WARNS?= 5
|
|
|
|
.include <bsd.lib.mk>
|