diff options
| author | Andy Polyakov <appro@openssl.org> | 2005-07-24 21:48:04 +0000 |
|---|---|---|
| committer | Andy Polyakov <appro@openssl.org> | 2005-07-24 21:48:04 +0000 |
| commit | b3836ed3cbeb9a5d735597e8a79ffea5894cb470 (patch) | |
| tree | 42c5dd3c0389ccd8cb1e90ebf6af476021cc3c57 /INSTALL.W32 | |
| parent | 47738cbad7fb27296dbb4f02393ba70854ce5cb7 (diff) | |
| download | openssl-b3836ed3cbeb9a5d735597e8a79ffea5894cb470.zip openssl-b3836ed3cbeb9a5d735597e8a79ffea5894cb470.tar.gz openssl-b3836ed3cbeb9a5d735597e8a79ffea5894cb470.tar.bz2 | |
Unify VC-32.pl and VC-CE.pl scripts and update INSTALL.W32.
Diffstat (limited to 'INSTALL.W32')
| -rw-r--r-- | INSTALL.W32 | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/INSTALL.W32 b/INSTALL.W32 index f18f249..a4b6700 100644 --- a/INSTALL.W32 +++ b/INSTALL.W32 @@ -287,3 +287,21 @@ (e.g. fopen()), and OpenSSL cannot change these; so in general you cannot rely on CRYPTO_malloc_init() solving your problem, and you should consistently use the multithreaded library. + + Linking your application + ------------------------ + + If you link with static OpenSSL libraries [those built with ms/nt.mak], + then you're expected to additionally link your application with + WSOCK32.LIB, ADVAPI32.LIB, GDI32.LIB and USER32.LIB. Those developing + non-interactive service applications might feel concerned about linking + with latter two, as they are justly associated with interactive desktop, + which is not available to service processes. The toolkit is designed + to detect in which context it's currently executed, GUI, console app + or service, and act accordingly, namely whether or not to actually make + GUI calls. + + If you link with OpenSSL .DLLs, then you're expected to include into + your application code small "shim" snippet, which provides glue between + OpenSSL BIO layer and your compiler run-time. Look up OPENSSL_Applink + reference page for further details. |