Lines Matching +refs:cc +refs:check +refs:function +refs:in +refs:lib
5 configuration in diverse ways:
21 different platforms and their capabilities. We organise them in a
25 files. The Configure script does check that a config file doesn't
56 given here instead of in 'cppflags' [4].
61 may be given here instead of in 'cppflags'
65 cc => The C compiler command, usually one of "cc",
89 in $(libdir)/pkgconfig/libcrypto.pc.
100 module_ldflags => Has the same function as the corresponding
148 letters in the "variant" identifier to uppercase
157 be used in the future. See further notes
168 source. This acts as a selector in build.info files.
170 source. This acts as a selector in build.info files.
179 - as index for targets found in shared_info.pl.
192 string in the list is the name of the build
203 to have the different variants in different
210 in different binary directories. This setting
211 works in conjunction with multilib.
213 bn_ops => Building options (was just bignum options in
230 limb size is implied in
235 in calculations;
257 by corresponding key values in the inheriting configuration.
263 If several configurations are given in the `inherit_from` array,
281 ignored => "This should not appear in the end result",
306 be `(unknown)`, in which case the user MUST give some compilation
317 Very roughly speaking, linking is done like this (words in braces
337 Historically, the target configurations came in form of a string with
341 "target" => "{cc}:{cflags}:{unistd}:{thread_cflag}:{sys_id}:{lflags}:
400 to be located in the source tree while files given through DEPEND are
401 expected to be located in the build tree)
414 In some cases, it's desirable to include some source files in the
448 be used in that case:
465 The expression in square brackets is interpreted as a string in perl,
470 conditions based on something in the passed variables, for example:
493 template file in `Configurations/` named like the build file, with
494 `.tmpl` appended, or in case of possible ambiguity, a combination of
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
549 intent => one of "lib", "dso", "bin" );
562 obj2lib - function that produces build file lines to build a
563 static library file ("libfoo.a" in Unix terms) from
568 obj2lib(lib => "PATH/TO/libfile",
571 'lib' has the intended library filename *without*
575 libobj2shlib - backward compatibility function that's used the
583 obj2shlib - function that produces build file lines to build a
584 shareable object library file ("libfoo.so" in Unix
590 lib => "PATH/TO/libfile",
594 'lib' has the base (static) library filename
595 *without* extension. This is useful in case
604 obj2dso - function that produces build file lines to build a
609 obj2dso(lib => "PATH/TO/libfile",
616 loaded in runtime (a "plugin"...).
618 obj2bin - function that produces build file lines to build an
634 in2script - function that produces build file lines to build a
654 ""; # Make sure no lingering values end up in the Makefile
660 Configure uses helper scripts in this directory:
665 These scripts are per platform family, to check the integrity of the
672 If the check succeeds, the script is expected to end with a non-zero
673 expression. If the check fails, the script can end with a zero, or