From: Andy Polyakov <appro@openssl.org>
Date: Wed, 18 May 2005 13:37:20 +0000 (+0000)
Subject: FAQ update to mention Applink [from HEAD].
X-Git-Tag: OpenSSL_0_9_8-beta1~9
X-Git-Url: https://git.librecmc.org/?a=commitdiff_plain;h=3dc2cc36e9dff2ebac0c0bafbc7fa63acd5df4bd;p=oweals%2Fopenssl.git

FAQ update to mention Applink [from HEAD].
---

diff --git a/FAQ b/FAQ
index 06faf91a5e..30913a11b3 100644
--- a/FAQ
+++ b/FAQ
@@ -652,6 +652,17 @@ by:
 Note that debug and release libraries are NOT interchangeable.  If you
 built OpenSSL with /MD your application must use /MD and cannot use /MDd.
 
+As per 0.9.8 the above limitation is eliminated for .DLLs. OpenSSL
+.DLLs compiled with some specific run-time option [we recommend the
+default /MD] can be deployed with application compiled with different
+option or even different compiler. But there is a catch! Instead of
+re-compiling OpenSSL toolkit, as you would have to with prior versions,
+you have to compile small C snippet with compiler and/or options of
+your choice. The snippet gets installed as
+<install-root>/include/openssl/applink.c and should be either added to
+your project or simply #include-d in one [and only one] of your source
+files. Failure to do either manifests itself as fatal "no
+OPENSSL_Applink" error.
 
 * How do I read or write a DER encoded buffer using the ASN1 functions?