Lines Matching refs:tools

3 Notes for NetBSD src/tools
9 Several programs that are part of NetBSD are also built as tools.  Such
17 build (e.g. "build.sh tools" or "make tools" from the top level src
22 tools installed in ${TOOLDIR}.
28 Programs that are built as tools need to be more portable than other
31 Most tools should restrict themselves to C language features that are
39 (src/tools/compat) described in a separate section below.
42 platform, then the tools build will fail.  This can be addressed by
44 src/tools/compat framework.  It is usually easy to add new macros or
45 functions to src/tools/compat, and that is usually better than adding
46 compatibility definitions to individual tools.
52 src/tools/compat provides a compatibility framework for use by tools.
57     A library containing functions that are needed by some tools.
61     A header file defining macros that are needed by some tools.
66     to define make variables appropriate for building tools.
70     so that tools will be linked with that library, and adds
71     -I${NETBSDSRCDIR}/tools/compat and -DHAVE_NBTOOL_CONFIG_H=1 to the
73     they are being built as tools.
76 Adapting Makefiles for use with tools
79 Makefiles under src/tools/*/Makefile should define the HOSTPROG
80 variable.  This is typically done by tools/Makefile.hostprog,
82 src/tools/*/Makefile.
84 Makefiles in the non-tools part of the src tree can test whether or not
94     CPPFLAGS+= -DWITH_FEATURE_X=0 # exclude feature X from tools build
99 Adapting Programs for use with tools
105 from src/tools/Makefile.host, which should be included directly or
106 indirectly from src/tools/*/Makefile.
112 In order to obtain the definitions provided by the tools compatibility
120 To omit features from the tools version of a program, the program
131 Makefiles for use with tools" for an example in which the Makefile