Lines Matching refs:file
20 build-file templates. See the section on build-file templates further
32 when they are, it's always with the file name extension `.o`), they are
34 file name extensions (such as `.so`, `.a`, `.exe`, etc) are never mentioned
35 in `build.info`. Their file name extensions will be inferred by the
36 build-file templates, adapted for the platform they are meant for (see
37 sections on `%unified_info` and build-file templates further down).
44 produced file, and their values are the source used to produce that
45 particular produced file, extra dependencies, include directories
63 This is the top directory `build.info` file, and it tells us that two
75 This is the `build.info` file in `apps/`, one may notice that all file
76 paths mentioned are relative to the directory the `build.info` file is
78 called `apps/openss` (the file name extension will depend on the
79 platform and is therefore not mentioned in the `build.info` file). It's
80 built from one source file, `apps/openssl.c`, and building it requires
94 This is the `build.info` file in `crypto/`, and it tells us a little more
98 file, but can make the info file easier to understand. This is to
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
111 `DEPEND[cversion.o]` mentions an object file. DEPEND indexes is the
118 This is the build.info file in `ssl/`, and it tells us that the
119 library `libssl` is built from the source file `ssl/tls.c`.
132 This is the `build.info` file in `engines/`, telling us that two modules
186 program depending on a library, or between an object file and some
187 extra source file.
205 depends => a hash table containing 'file' => [ 'dependency' ... ]
212 generate => a hash table containing 'file' => [ 'generator' ... ]
216 includes => a hash table containing 'file' => [ 'include' ... ]
220 install => a hash table containing 'type' => [ 'file' ... ] pairs.
234 sources => a hash table containing 'file' => [ 'sourcefile' ... ]
408 Build-file templates
411 Build-file templates are essentially build-files (such as `Makefile` on
416 functions that are used to generates specific build-file rules, to
421 generatesrc - function that produces build file lines to generate
422 a source file from some input.
434 'src' has the name of the file to be generated.
436 generate the file, of which the first item is
437 expected to be the file to generate from.
439 exactly how to apply that file and how to capture
442 file itself depends on. 'incs' and 'deps' are
445 end product (the file indicated by 'src'). 'intent'
446 indicates what the generated file is going to be
449 src2obj - function that produces build file lines to build an
450 object file from source files and associated data.
460 'obj' has the intended object file with `.o`
464 object file, with the first item being the source
465 file that directly corresponds to the object file.
467 is a list of include file directories. Finally,
468 'intent' indicates what this object file is going
471 obj2lib - function that produces build file lines to build a
472 static library file ("libfoo.a" in Unix terms) from
480 'lib' has the intended library file name *without*
492 obj2shlib - function that produces build file lines to build a
493 shareable object library file ("libfoo.so" in Unix
503 'lib' has the base (static) library file name
513 obj2dso - function that produces build file lines to build a
514 dynamic shared object file from object files.
527 obj2bin - function that produces build file lines to build an
528 executable file from object files.
536 'bin' has the intended executable file name
543 in2script - function that produces build file lines to build a
544 script file from some input.
551 'script' has the intended script file name.
555 Along with the build-file templates is the driving template
559 functions defined in the build-file template.
604 together and written to the resulting build-file.
