Lines Matching full:program
87 system permits the developer to concentrate on writing the program,
90 program using simple rules rather than complex Makefiles.
94 step process. The program builder need not install any special tools in
95 order to build the program.
104 tools. Program developers must build and install all of these tools.
108 program, and a C compiler.
115 a system for describing how to build a program, permitting the
147 * The Metaconfig program, by Larry Wall, Harlan Stenn, and Raphael
154 * The autoconf program, by David MacKenzie.
156 The Metaconfig program is still used for Perl and a few other
168 Most programs are built using the make program, which requires the
180 requires that the builder install the new BSD make program.
184 Makefile which could be used by the standard make program. In 1995, Tom
317 If you have an existing body of code, the `autoscan' program may
446 `aclocal' program will be able to find them.
486 If your package builds a program, then in the directory where that
487 program is built you will normally want a line like
488 bin_PROGRAMS = PROGRAM
489 where PROGRAM is the name of the program. You will then want a line
493 program (e.g., `foo.c').
518 is possible to use other names if the program or library should be
556 Normally the `autoheader' program will inform you of any such
598 tree, you will need to run the `libtoolize' program to copy the libtool
622 Suppose we want to write a simple version of `touch'. Our program,
625 the file to the current time. We want this program to be highly
700 In our `Makefile', we don't provide any way to install the program.
701 This doesn't matter much for such a simple example, but a real program
711 Here is our second try at this program.
821 `install' program which may be used, and which supports optional
837 For our third try at this program, we will write a `configure.in'
887 This means that we should build a single program name `poke'. It
889 earlier. The program `poke' is built from the source file `poke.c'.
1095 This file is created by the `aclocal' program, based on the
1110 included by your program. This permits your C code to use
1183 This is the file which make will read to build the program. The
1256 A shell script which installs a program. This is used if the
1291 conflicts when using a parallel make program.
1705 both a host program (since it runs on the host) and a target
1784 For every subdirectory DIR which holds a host library or program,
1785 the `Makefile' target `all-DIR' will build that library or program.
1845 program which will run on a system which is different from the system on
1869 While running on a GNU/Linux, you can build a program which will run
1871 to build the program.
1873 Of course, you could not run the resulting program on your GNU/Linux
1903 For example, if you are building a Solaris program on a GNU/Linux
1928 In order to configure a program for a Canadian Cross build, you must
1930 program.
1937 host system is where the resulting program will run. Therefore, you
1989 cross tools which you want to use to build the program. This is done by
2001 For example, if you are building a Solaris program on a GNU/Linux
2017 * Standard Cygnus CCross:: Building a Normal Program.
2018 * Cross Cygnus CCross:: Building a Cross Program.
2023 6.6.1 Building a Normal Program
2051 6.6.2 Building a Cross Program
2062 built target compiler will be a program which runs on the host system,
2120 If you want to make it possible to build a program you are developing
2168 test program. This will fail in a Canadian Cross, because the program
2182 your program that the test could not be performed at configure time.
2199 use a subsidiary program to generate code or data which you will then
2200 include in your real program.
2202 If you compile this subsidiary program using `$(CC)' in the usual
2204 build a program for the host system, but the program is being built on
2221 run on the build system and into the final program. This approach may
2253 Cygnus configure does not use any generated files; there is no program
