Lines Matching refs:files
7 The unified scheme takes all its data from the `build.info` files seen
8 throughout the source tree. These files hold the minimum information
9 needed to build end product files from diverse sources. See the
10 section on `build.info` files below.
12 From the information in `build.info` files, `Configure` builds up an
18 generate the rules for building end product files as well as
19 intermediary files with the help of a few functions found in the
23 build.info files
26 As mentioned earlier, `build.info` files are meant to hold the minimum
27 information needed to build output files, and therefore only (with a
29 as scripts, library files and programs) and source files (such as C
30 files, C header files, assembler files, etc). Intermediate files such
31 as object files are rarely directly referred to in `build.info` files (and
50 scripts to be produced, source files, dependencies, etc etc etc.
102 source files, `crypto/aes.c`, `crypto/evp.c` and `crypto/cversion.c`.
105 also shows the possibility to declare how some files are generated
107 can be declared to depend on other files, in this case a perl module.
142 When `Configure` digests these `build.info` files, the accumulated
180 The indexes for `SOURCE` must only be end product files, such as
182 only be source files (possibly generated).
184 `INCLUDE` and `DEPEND` shows a relationship between different files
185 (usually produced files) or between files and directories, such as a
189 When `Configure` processes the `build.info` files, it will take it as
192 that all built files and up in the build directory and that all source
193 files are to be found in the source tree, if they can be found there.
194 `Configure` will assume that source files that can't be found in the
207 variables in build.info files.
210 the MODULES variable in build.info files.
214 variables in build.info files.
218 variables in build.info files.
222 'scripts', and the array of files list the files of
226 the LIBS variable in build.info files.
229 the PROGRAMS variable in build.info files.
232 the SCRIPTS variable in build.info files.
236 variables in build.info files. Object files are
237 mentioned in this hash table, with source files from
238 SOURCE variables, and AS source files for programs and
243 files (object files) for building shared libraries.
245 As an example, here is how the `build.info` files example from the
411 Build-file templates are essentially build-files (such as `Makefile` on
414 rules needed to build end product files and intermediary files alike.
417 build static libraries from object files, to build shared libraries
418 from static libraries, to programs from object files and libraries,
441 are include directories and files that the generator
443 include directories and files that are used if $(CC)
450 object file from source files and associated data.
463 'srcs' has the list of source files to build the
473 object files.
482 has the list of object files to build this library.
490 object files. Attempting to do this will fail.
494 terms) from the corresponding object files.
505 supporting files are needed (such as import
511 object files to build this library.
514 dynamic shared object file from object files.
528 executable file from object files.
538 that. 'objs' has the list of object files to build
539 this library. 'deps' has the list of library files
552 'sources' has the list of source files to build the
558 programs and all intermediate files, using the rule generating
