To build an application that uses the Secure Sockets Package of the Secure Communication Module, you must link to:
The Essential Tools Module library
The following package libraries from the Threads Module: Smart Pointer (pointer), Synchronization (sync), Thread-compatible Exceptions (threxcept), and Execution Tracing (trace)
The Secure Communication Module (secsock) package library, and the Essential Networking Module (network) package library.
The underlying cryptographic library (OpenSSL)
For specific information about linking to this library for static and dynamic builds, see the next two sections.
System libraries
When building a static Secure Sockets Package application, you must link to the static version of the underlying cryptographic package.
For OpenSSL, link to libeay32.lib and ssleay32.lib on Windows, libcrypto.a and libssl.a on UNIX.
OpenSSL can be built as a dynamic library, so you link to both the SourcePro C++ and OpenSSL dynamic libraries.
On Windows, the libraries you link to are named the same as the static versions, libeay32.lib and ssleay32.lib. However, the dynamic libraries are much smaller than their static equivalents because they simply point to the main OpenSSL DLL library that contains the actual code. Be careful to point to the dynamic versions of these libraries.
On UNIX platforms, the names of the dynamic libraries are libcrypto.so and libssl.so (or whatever extension your platform uses for shared objects).
Copyright © Rogue Wave Software, Inc. All Rights Reserved.
The Rogue Wave name and logo, and SourcePro, are registered trademarks of Rogue Wave Software. All other trademarks are the property of their respective owners.
Contact Rogue Wave about documentation or support issues.