OpenNJet实现了NGINX云原生功能增强、安全加固和代码重构，利用动态加载机制可以实现不同的产品形态，如Web服务器等等

Intro ===== This directory contains a few sets of files that are used for configuration in diverse ways: *.conf Target platform configurations, please read 'Configurations of OpenSSL target platforms' for more information. *.tmpl Build file templates, please read 'Build-file programming with the "unified" build system' as well as 'Build info files' for more information. *.pm Helper scripts / modules for the main `Configure` script. See 'Configure helper scripts for more information. Configurations of OpenSSL target platforms ========================================== Configuration targets are a collection of facts that we know about different platforms and their capabilities. We organise them in a hash table, where each entry represent a specific target. Note that configuration target names must be unique across all config files. The Configure script does check that a config file doesn't have config targets that shadow config targets from other files. In each table entry, the following keys are significant: inherit_from => Other targets to inherit values from. Explained further below. [1] template => Set to 1 if this isn't really a platform target. Instead, this target is a template upon which other targets can be built. Explained further below. [1] sys_id => System identity for systems where that is difficult to determine automatically. enable => Enable specific configuration features. This MUST be an array of words. disable => Disable specific configuration features. This MUST be an array of words. Note: if the same feature is both enabled and disabled, disable wins. as => The assembler command. This is not always used (for example on Unix, where the C compiler is used instead). asflags => Default assembler command flags [4]. cpp => The C preprocessor command, normally not given, as the build file defaults are usually good enough. cppflags => Default C preprocessor flags [4]. defines => As an alternative, macro definitions may be given here instead of in 'cppflags' [4]. If given here, they MUST be as an array of the string such as "MACRO=value", or just "MACRO" for definitions without value. includes => As an alternative, inclusion directories may be given here instead of in 'cppflags' [4]. If given here, the MUST be an array of strings, one directory specification each. cc => The C compiler command, usually one of "cc", "gcc" or "clang". This command is normally also used to link object files and libraries into the final program. cxx => The C++ compiler command, usually one of "c++", "g++" or "clang++". This command is also used when linking a program where at least one of the object file is made from C++ source. cflags => Defaults C compiler flags [4]. cxxflags => Default C++ compiler flags [4]. If unset, it gets the same value as cflags. (linking is a complex thing, see [3] below) ld => Linker command, usually not defined (meaning the compiler command is used instead). (NOTE: this is here for future use, it's not implemented yet) lflags => Default flags used when linking apps, shared libraries or DSOs [4]. ex_libs => Extra libraries that are needed when linking shared libraries, DSOs or programs. The value is also assigned to Libs.private in $(libdir)/pkgconfig/libcrypto.pc. shared_cppflags => Extra C preprocessor flags used when processing C files for shared libraries. shared_cflag => Extra C compiler flags used when compiling for shared libraries, typically something like "-fPIC". shared_ldflag => Extra linking flags used when linking shared libraries. module_cppflags module_cflags module_ldflags => Has the same function as the corresponding 'shared_' attributes, but for building DSOs. When unset, they get the same values as the corresponding 'shared_' attributes. ar => The library archive command, the default is "ar". (NOTE: this is here for future use, it's not implemented yet) arflags => Flags to be used with the library archive command. On Unix, this includes the command letter, 'r' by default. ranlib => The library archive indexing command, the default is 'ranlib' it it exists. unistd => An alternative header to the typical '<unistd.h>'. This is very rarely needed. shared_extension => File name extension used for shared libraries. obj_extension => File name extension used for object files. On unix, this defaults to ".o" (NOTE: this is here for future use, it's not implemented yet) exe_extension => File name extension used for executable files. On unix, this defaults to "" (NOTE: this is here for future use, it's not implemented yet) shlib_variant => A "variant" identifier inserted between the base shared library name and the extension. On "unixy" platforms (BSD, Linux, Solaris, MacOS/X, ...) this supports installation of custom OpenSSL libraries that don't conflict with other builds of OpenSSL installed on the system. The variant identifier becomes part of the SONAME of the library and also any symbol versions (symbol versions are not used or needed with MacOS/X). For example, on a system where a default build would normally create the SSL shared library as 'libssl.so -> libssl.so.1.1' with the value of the symlink as the SONAME, a target definition that sets 'shlib_variant => "-abc"' will create 'libssl.so -> libssl-abc.so.1.1', again with an SONAME equal to the value of the symlink. The symbol versions associated with the variant library would then be