Lines Matching refs:from
7 The unified scheme takes all its data from the `build.info` files seen
9 needed to build end product files from diverse sources. See the
17 [`Configurations/common.tmpl`](common.tmpl) uses the data from `%unified_info` to
80 built from one source file, `apps/openssl.c`, and building it requires
82 from the point of view of the `apps/` directory), and that the program
101 This `build.info` file informs us that `libcrypto` is built from a few
103 It also shows us that building the object file inferred from
119 library `libssl` is built from the source file `ssl/tls.c`.
191 If the build tree is separate from the source tree, it will assume
206 pairs. These are directly inferred from the DEPEND
209 modules => a list of modules. These are directly inferred from
213 pairs. These are directly inferred from the GENERATE
217 pairs. These are directly inferred from the INCLUDE
225 libraries => a list of libraries. These are directly inferred from
228 programs => a list of programs. These are directly inferred from
231 scripts => a list of scripts. There are directly inferred from
235 pairs. These are indirectly inferred from the SOURCE
237 mentioned in this hash table, with source files from
245 As an example, here is how the `build.info` files example from the
417 build static libraries from object files, to build shared libraries
418 from static libraries, to programs from object files and libraries,
422 a source file from some input.
437 expected to be the file to generate from.
450 object file from source files and associated data.
472 static library file ("libfoo.a" in Unix terms) from
486 expected to build the shared library from the
488 NOTE: building a shared library from a static
494 terms) from the corresponding object files.
514 dynamic shared object file from object files.
528 executable file from object files.
544 script file from some input.
553 resulting script from.
603 The returned strings from all those calls are then concatenated
