Lines Matching refs:build

11                 programming with the "unified" build system' as well
52 given, as the build file defaults are
138 where a default build would normally create the SSL
159 dso_scheme => The type of dynamic shared objects to build
168 source. This acts as a selector in build.info files.
170 source. This acts as a selector in build.info files.
186 build_scheme => The scheme used to build up a Makefile.
188 with the name of the build scheme.
192 string in the list is the name of the build
194 Currently recognised build scheme is "unified".
195 For the "unified" build scheme, this item
218 such as the type of integers used to build up
261 cannot be used as build targets.
352 The `build.info` files that are spread over the source tree contain the
353 minimum information needed to build and distribute OpenSSL. It uses a
357 For every `build.info` file, all file references are relative to the
358 directory of the `build.info` file for source files, and the
359 corresponding build directory for built files if the build tree
366 directory for the current `build.info` file and the corresponding build
367 directory, all relative to the top of the build tree.
369 `Configure` only knows inherently about the top `build.info` file. For
384 without extensions. The build file templates will figure them out.
401 expected to be located in the build tree)
409 only used when supported. For example, native Windows build doesn't
420 include paths the build of their source files should use:
437 build file template to define exactly how those command lines should
454 Finally, you can have some simple conditional use of the `build.info`
480 Build-file programming with the "unified" build system
486 To use the "unified" build system, the target configuration needs to
493 template file in `Configurations/` named like the build file, with
501 The build-file template is processed with the perl module
507 The build-file template is expected to define at least the following
511 generatesrc - function that produces build file lines to generate
540 src2obj - function that produces build file lines to build an
554 'srcs' has the list of source files to build the
562 obj2lib - function that produces build file lines to build a
573 has the list of object files to build this library.
577 expected to build the shared library from the
583 obj2shlib - function that produces build file lines to build a
602 object files to build this library.
604 obj2dso - function that produces build file lines to build a
615 intent is to build a shareable library that can be
618 obj2bin - function that produces build file lines to build an
629 that. 'objs' has the list of object files to build
634 in2script - function that produces build file lines to build a
643 'sources' has the list of source files to build the
646 In all cases, file file paths are relative to the build tree top, and
647 the build file actions run with the build tree top as current working
651 you thing is appropriate for the resulting build file. If nothing