Lines Matching refs:as
13 information database as a hash table called `%unified_info`, which is
15 or may not be the same as the source tree).
18 generate the rules for building end product files as well as
29 as scripts, library files and programs) and source files (such as C
31 as object files are rarely directly referred to in `build.info` files (and
34 file name extensions (such as `.so`, `.a`, `.exe`, etc) are never mentioned
40 end products. There are variants for them with `_NO_INST` as suffix
97 really unnecessary as it's already mentioned in the top `build.info`
139 the library `libcrypto`. Finally, only `dasync` is being installed, as
180 The indexes for `SOURCE` must only be end product files, such as
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
195 source tree (such as `crypto/bildinf.h` in the example above) are
242 a hash table just like 'sources', but only as source
403 other things it depends on (such as `libssl`). All those dependencies
404 need to be built as well, using the same logic, so to build `libssl`,
405 we need to build `ssl/tls.o` as well as `libcrypto`, and to build the
411 Build-file templates are essentially build-files (such as `Makefile` on
444 is used as an intermediary step when generating the
485 same way as obj2shlib (described next), and was
489 library is now DEPRECATED, as they no longer share
505 supporting files are needed (such as import
523 This is almost the same as obj2shlib, but the
561 As an example with the smaller `build.info` set we've seen as an
