Lines Matching full:tool
173 The X Window system is built using the imake tool, which uses a
175 tool which was developed using imake requires that the builder have
205 Most readers of this document should already know how to build a tool by
209 Building a tool is normally as simple as running `configure'
322 Another handy tool for an existing body of code is `ifnames'. This
448 The different macro prefixes indicate which tool defines the macro.
988 are plain text and the tool names are enclosed by `*' characters (e.g.,
989 `autoheader' is the name of a tool, not the name of a file).
1273 A shell script used if some tool is missing entirely. This is
1412 compilation" tools. A cross compilation tool is a tool which runs on
1440 Although the debugger is not strictly speaking a compilation tool,
1472 speak of the target of a tool like `bison' or `make'.
1475 native compilation tool, it is still meaningful to speak of a target.
1476 For a native tool, the target is the same as the host. For example, for
1491 host system, and the package is not a cross compilation tool and
1525 If you want to build a cross compilation tool, you must specify the
1540 When writing `configure.in' for a cross compilation tool, you will need
1572 the two versions of SunOS may be unimportant for your tool. However,
1577 to configure a cross compilation tool.
1584 in the file system, such as a directory name or part of a tool name.
1585 It also includes any tool output, unless it is clearly labelled as the
1587 `--target' option to specify how the tool will appear to the outside
1599 `--target' option, and thus is building a native tool, no prefix is
1663 which compiler you are going to use to build a tool; otherwise, the
1797 gcc, the target compiler, is required to configure the tool. Every
2027 appropriate environment variables are automatically set to `HOST-TOOL',
2028 where HOST is the value used for the `--host' option, and TOOL is the
2029 name of the tool (e.g., `gcc', `as', etc.). These tools must be on
