Lines Matching +full:- +full:- +full:build
10 *.tmpl Build file templates, please read 'Build-file
11 programming with the "unified" build system' as well
12 as 'Build info files' for more information.
52 given, as the build file defaults are
95 like "-fPIC".
138 where a default build would normally create the SSL
139 shared library as 'libssl.so -> libssl.so.1.1' with
141 definition that sets 'shlib_variant => "-abc"' will
142 create 'libssl.so -> libssl-abc.so.1.1', again with
149 and all non-alphanumeric characters to '_'.
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.
172 even when 'no-asm' is given, even though it contains
179 - as index for targets found in shared_info.pl.
180 - as linker script generation selector.
182 should end with '-shared', and this suffix will be
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
202 32-bit and a 64-bit variant), this is used
208 (typically a 32-bit and a 64-bit variant),
218 such as the type of integers used to build up
233 but 64-bit 'unsigned long
261 cannot be used as build targets.
305 specifies `no-threads`. The value of the key `thread_scheme` may
312 - shared libraries; that would be libcrypto and libssl.
313 - shared objects (sometimes called dynamic libraries); that would
315 - applications; those are apps/openssl and all the test apps.
322 {ld} $(CFLAGS) {lflags} {shared_ldflag} -o libfoo.so \
326 {ld} $(CFLAGS) {lflags} {module_ldflags} -o libeng.so \
327 blah1.o blah2.o -lcrypto {ex_libs}
330 {ld} $(CFLAGS) {lflags} -o app \
331 app1.o utils.o -lssl -lcrypto {ex_libs}
349 Build info files
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
363 Text::Template, using the delimiters `{-` and `-}`. The hashes
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
412 `no-shared`.
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`
472 IF[{- $disabled{shared} -}]
480 Build-file programming with the "unified" build system
483 "Build files" are called `Makefile` on Unix-like operating systems,
486 To use the "unified" build system, the target configuration needs to
493 template file in `Configurations/` named like the build file, with
497 `Configurations/Makefile.tmpl` or `Configurations/unix-Makefile.tmpl`.
498 In case both `Configurations/unix-Makefile.tmpl` and
501 The build-file template is processed with the perl module
502 Text::Template, using `{-` and `-}` as delimiters that enclose the
503 perl code fragments that generate configuration-dependent content.
507 The build-file template is expected to define at least the following
508 perl functions in a perl code fragment enclosed with `{-` and `-}`.
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.
575 libobj2shlib - backward compatibility function that's used the
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
655 -}
663 ---------------
667 either `{build_platform}-{build_file}-checker.pm` or
668 `{build_platform}-checker.pm`, where `{build_platform}` is the second
672 If the check succeeds, the script is expected to end with a non-zero