freebsd-dev/lib/libucl/Makefile

# $FreeBSD$

LIBUCL=	${.CURDIR}/../../contrib/libucl

LIB=		ucl
PRIVATELIB=	true
SHLIB_MAJOR=	1
SRCS=		ucl_emitter.c \
		ucl_hash.c \
		ucl_parser.c  \
		ucl_util.c \
		xxhash.c

.PATH:		${LIBUCL}/src

WARNS=		1
CFLAGS+=	-I${LIBUCL}/include \
		-I${LIBUCL}/src \
		-I${LIBUCL}/uthash

.include <bsd.lib.mk>
Import libucl into head UCL is heavily infused by nginx configuration as the example of a convenient configuration system. However, UCL is fully compatible with JSON format and is able to parse json files. UCL is used by pkg(8) for its configuration file as well for the manifest format in packages, it will be used in base for the pkg boostrap (signature checking and configuration file parsing.) libucl has been developped and is maintained by vsevolod@ 2014-02-23 21:49:21 +00:00			`# $FreeBSD$`

			`LIBUCL= ${.CURDIR}/../../contrib/libucl`

			`LIB= ucl`
			`PRIVATELIB= true`
			`SHLIB_MAJOR= 1`
			`SRCS= ucl_emitter.c \`
			`ucl_hash.c \`
			`ucl_parser.c \`
			`ucl_util.c \`
			`xxhash.c`

			`.PATH: ${LIBUCL}/src`

Lower the level of WARNS to fix build with gcc 2014-02-23 22:50:22 +00:00			`WARNS= 1`
Import libucl into head UCL is heavily infused by nginx configuration as the example of a convenient configuration system. However, UCL is fully compatible with JSON format and is able to parse json files. UCL is used by pkg(8) for its configuration file as well for the manifest format in packages, it will be used in base for the pkg boostrap (signature checking and configuration file parsing.) libucl has been developped and is maintained by vsevolod@ 2014-02-23 21:49:21 +00:00			`CFLAGS+= -I${LIBUCL}/include \`
			`-I${LIBUCL}/src \`
			`-I${LIBUCL}/uthash`

			`.include <bsd.lib.mk>`