Apps: divide the modules in direct command modules, support library and init
authorRichard Levitte <levitte@openssl.org>
Wed, 31 Jan 2018 13:15:52 +0000 (14:15 +0100)
committerRichard Levitte <levitte@openssl.org>
Wed, 31 Jan 2018 22:45:12 +0000 (23:45 +0100)
commitd6baf09fe0c9efe4fe87e16fed088b9ce2b4c3f1
treee100416ad6f2ea885d930914c07646877f91a432
parentdab2cd68e7cc304c9b1a4e7cee18a98711771a53
Apps: divide the modules in direct command modules, support library and init

Most modules are direct implementations of openssl application
sub-commands, but some constitute a support library, which can be used
by more than one program (and is, incidently, by test/uitest).

For practical purposes, we place the support library modules in a
private, static library.

Finally, there are some modules that don't have direct references in
the rest of the apps code, but are still crucial.  See them as some
kind of extra crt0 or similar for your platform.

Inspiration from David von Oheimb

Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/5222)
Configurations/00-base-templates.conf
Configurations/10-main.conf
Configurations/README
Configurations/windows-checker.pm
apps/build.info