f1f5ee17b6
If application uses any of Windows-specific interfaces, make it application developer's respondibility to include <windows.h>. Rationale is that <windows.h> is quite "toxic" and is sensitive to inclusion order (most notably in relation to <winsock2.h>). It's only natural to give complete control to the application developer. Reviewed-by: Rich Salz <rsalz@openssl.org> Reviewed-by: Matt Caswell <matt@openssl.org> |
||
|---|---|---|
| .. | ||
| apps | ||
| crypto | ||
| HOWTO | ||
| ssl | ||
| dir-locals.example.el | ||
| fingerprints.txt | ||
| openssl-c-indent.el | ||
| README | ||
README This file
fingerprints.txt
PGP fingerprints of authoried release signers
standards.txt
Moved to the web, https://www.openssl.org/docs/standards.html
HOWTO/
A few how-to documents; not necessarily up-to-date
apps/
The openssl command-line tools; start with openssl.pod
ssl/
The SSL library; start with ssl.pod
crypto/
The cryptographic library; start with crypto.pod
Formatted versions of the manpages (apps,ssl,crypto) can be found at
https://www.openssl.org/docs/manpages.html