diff options
| author | Richard Levitte <levitte@openssl.org> | 2015-05-18 14:31:49 +0200 |
|---|---|---|
| committer | Richard Levitte <levitte@openssl.org> | 2016-01-22 00:58:56 +0100 |
| commit | 88087414def54cd55dfebc172f17f79ed7d3034a (patch) | |
| tree | f375deb9a16124f804d8b676abe51da727881c26 /Configurations/README | |
| parent | 9e0724a1805fba20a897f6c7f95336f0da017ccf (diff) | |
Refactor config - @MK1MF_Builds out, general build scheme in
Time to get rid of @MK1MF_Builds and introduce a more flexible
'build_scheme' configuration key. Its value may be a string or an
array of strings, meaning we need to teach resolve_config how to
handle ARRAY referenses.
The build scheme is a word that selects a function to create the
appropriate result files for a certain configuration. Currently valid
build schemes aer "mk1mf" and "unixmake", the plan is however to add
at least one other for a more universal build scheme.
Incidently, this also adds the functions 'add' and 'add_before', which
can be used in a configuration, so instead of having to repeatedly
write a sub like this:
key1 => sub { join(" ", @_, "myvalues"); },
key2 => sub { join(" ", "myvalues", @_); },
one could write this:
key1 => add(" ", "myvalues"),
key2 => add_before(" ", "myvalues"),
The good point with 'add' and 'add_before' is that they handle
inheritances where the values are a misture of scalars and ARRAYs. If
there are any ARRAY to be found, the resulting value will be an ARRAY,
otherwise it will be a scalar with all the incoming valued joined
together with the separator given as first argument to add/add_before.
Reviewed-by: Rich Salz <rsalz@openssl.org>
Diffstat (limited to 'Configurations/README')
| -rw-r--r-- | Configurations/README | 12 |
1 files changed, 10 insertions, 2 deletions
diff --git a/Configurations/README b/Configurations/README index e1327e57f9..df55d71549 100644 --- a/Configurations/README +++ b/Configurations/README @@ -97,8 +97,16 @@ In each table entry, the following keys are significant: shared_target => The shared library building method used. This is a target found in Makefile.shared. build_scheme => The scheme used to build up a Makefile. - (NOTE: this is here for future use, it's - not implemented yet) + In its simplest form, the value is a string + with the name of the build scheme. + The value may also take the form of a list + of strings, if the build_scheme is to have + some options. In this case, the first + string in the list is the name of the build + scheme. + Currently recognised build schemes are + "mk1mf" and "unixmake". Others may appear + in the future. multilib => On systems that support having multiple implementations of a library (typically a |