freebsd-dev/tools/bsdbox/Makefile.telnetd

# Build telnetd
# Question - why is telnetds objects ending up in the srcdir? -adrian

# This won't work yet - because telnetd relies on libtelnet.a which includes
# kerberos support by default; building telnetd without kerberos support
# requires the cross-build world to be built the same.
#   -adrian

# $FreeBSD$

CRUNCH_PROGS_libexec+=	telnetd
CRUNCH_PROGS_usr.bin+=	telnet
CRUNCH_LIBS+=		-lkrb5 -lhx509 -lasn1 -lcom_err -lroken -ltelnetd
# CRUNCH_BUILDOPTS_telnetd=	MK_KERBEROS_SUPPORT=no
Import the first cut of "bsdbox". This uses the existing crunchgen infrastructure to build a series of tools designed to replace the base and networking tools on an embedded system. It reuses 'bsd.crunchgen.mk' to drive the actual file creation. The rescue build system also uses this. Unlike busybox, it doesn't include its own source - instead, it just builds from the sources in /usr/src/ and leverages the existing BSD framework. Thie is still quite messy and could do with a whole lot of cleaning up. However it is proving to be very useful with my current build framework, allowing me to build binary root images that are about 30% less than simply cherrypicking files and libraries from an installworld. 2012-01-06 00:56:31 +00:00			`# Build telnetd`
			`# Question - why is telnetds objects ending up in the srcdir? -adrian`

			`# This won't work yet - because telnetd relies on libtelnet.a which includes`
			`# kerberos support by default; building telnetd without kerberos support`
			`# requires the cross-build world to be built the same.`
			`# -adrian`

			`# $FreeBSD$`

			`CRUNCH_PROGS_libexec+= telnetd`
			`CRUNCH_PROGS_usr.bin+= telnet`
			`CRUNCH_LIBS+= -lkrb5 -lhx509 -lasn1 -lcom_err -lroken -ltelnetd`
use MK_KERBEROS=no in preference to WITHOUT_KERBEROS 2014-04-05 17:54:50 +00:00			`# CRUNCH_BUILDOPTS_telnetd= MK_KERBEROS_SUPPORT=no`