header files
* a supported operating system
- For more details regarding specific platforms, there are these notes
- available:
+ For additional platform specific requirements and other details,
+ please read one of these:
* NOTES.VMS (OpenVMS)
* NOTES.WIN (any Windows except for Windows CE)
on a platform that does not support AFALG.
no-asm
- Do not use assembler code.
+ Do not use assembler code. On some platforms a small amount
+ of assembler code may still be used.
no-async
Do not build support for async operations.
Don't build the padlock engine.
no-makedepend
- ??
+ Don't generate dependencies.
no-multiblock
Don't build support for writing multiple records in one
sctp
Build support for SCTP
- shared
- In addition to the usual static libraries, create shared
- libraries on platforms where it's supported. See "Note on
- shared libraries" below.
+ no-shared
+ Do not create shared libraries, only static ones. See "Note
+ on shared libraries" below.
no-sock
Don't build support for socket BIOs
compiled with CPU_ENABLE_SSE, and there is a way to
disengage SSE2 code pathes upon application start-up,
but if you aim for wider "audience" running such kernel,
- consider no-sse2. Both 386 and no-the asm options imply
+ consider no-sse2. Both the 386 and no-asm options imply
no-sse2.
enable-ssl-trace
Note on shared libraries
------------------------
- Shared libraries have certain caveats. Binary backward compatibility
- can't be guaranteed before OpenSSL version 1.0. The only reason to
- use them would be to conserve memory on systems where several programs
- are using OpenSSL.
-
- For most systems, the OpenSSL Configure script knows what is needed to
- build shared libraries for libcrypto and libssl. On these systems,
- the shared libraries are currently not created by default, but giving
- the option "shared" will get them created.
+ For most systems the OpenSSL Configure script knows what is needed to
+ build shared libraries for libcrypto and libssl. On these systems
+ the shared libraries will be created by default. This can be suppressed and
+ only static libraries created by using the "no-shared" option. On systems
+ where OpenSSL does not know how to build shared libraries the "no-shared"
+ option will be forced and only static libraries will be created.
Note on random number generation
--------------------------------