FAQ update to mention Applink.
This commit is contained in:
parent
c50226594d
commit
788e67e227
11
FAQ
11
FAQ
@ -652,6 +652,17 @@ by:
|
|||||||
Note that debug and release libraries are NOT interchangeable. If you
|
Note that debug and release libraries are NOT interchangeable. If you
|
||||||
built OpenSSL with /MD your application must use /MD and cannot use /MDd.
|
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?
|
* How do I read or write a DER encoded buffer using the ASN1 functions?
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user