Move libapps headers into their own directory
authorRichard Levitte <levitte@openssl.org>
Tue, 12 Feb 2019 10:37:43 +0000 (11:37 +0100)
committerRichard Levitte <levitte@openssl.org>
Wed, 13 Feb 2019 03:47:11 +0000 (04:47 +0100)
commit5674466e007d892ec55441059b3763abd5dd5440
tree00168bff4d96171d868d9a06eddc99d2f6932d6d
parent7f4268bff3cf49b96d25bfd83013ee310c31520b
Move libapps headers into their own directory

This got triggered by test/testutil.h including ../apps/opt.h.

Some compilers do all inclusions from the directory of the C file
being compiled, so when a C file includes a header file with a
relative file spec, and that header file also includes another header
file with a relative file spec, the compiler no longer follows.

As a specific example, test/testutil/basic_output.c included
../testutil.h.  Fine so far, but then, test/testutil.h includes
../apps/opt.h, and the compiler ends up trying to include (seen from
the source top) test/apps/opt.h rather than apps/opt.h, and fails.

The solution could have been to simply add apps/ as an inclusion
directory.  However, that directory also has header files that have
nothing to do with libapps, so we take this a bit further, create
apps/include and move libapps specific headers there, and then add
apps/include as inclusion directory in the build.info files where
needed.

Reviewed-by: Paul Yang <yang.yang@baishancloud.com>
(Merged from https://github.com/openssl/openssl/pull/8210)
apps/build.info
apps/include/apps.h [moved from apps/apps.h with 100% similarity]
apps/include/apps_ui.h [moved from apps/apps_ui.h with 100% similarity]
apps/include/fmt.h [moved from apps/fmt.h with 100% similarity]
apps/include/opt.h [moved from apps/opt.h with 100% similarity]
apps/include/s_apps.h [moved from apps/s_apps.h with 100% similarity]
test/build.info
test/testutil.h