Lines Matching refs:F
69 =head2 F<build.info> files
71 F<build.info> files are meta data files for OpenSSL's built file
94 F<build.info> files are platform agnostic. This means that there is
112 F<build.info> files. The build file generators are responsible for
143 finally that there are more F<build.info> files in subdirectories
153 F<foo.c> and F<details.c>, and that it depends on the library
231 F<build.info> files include a very simple condition system, involving
257 F<build.info> handles simple variables. They are defined by
292 F<build.info> files that are digested. There are two exceptions,
293 F<build.info> variables and B<SUBDIRS> statement, for which the scope
294 is the F<build.info> file they are in.
298 Whenever a F<build.info> file is read, it is passed through the Perl
304 text form. This is useful to get dynamically generated F<build.info>
322 in scope within the whole F<build.info> file.
343 If F<build.info> statements have been skipped over to this point since
344 the corresponding B<IF> or B<ELSIF>, F<build.info> processing starts
363 This instructs the F<build.info> reader to also read the F<build.info>
365 relative to the location of the current F<build.info> file.
478 L</Perl nuggets> mechanism that is used to read F<build.info> files).
508 on the module F<OpenSSL::foo> - a.k.a. F<OpenSSL/foo.pm> - which lives in
509 F<util/perl>, it feasible to have something like this:
632 F<Makefile>; on VMS, this is typically F<descrip.mms>.
637 data collected from F<build.info> files.
641 Any F<build.info> statement of the form B<I<KEYWORD>>=I<values>, with
646 Any F<build.info> statement of the form B<I<KEYWORD>[>I<items>B<]=>I<values>,
