C++ Based OPC UA Client/Server SDK  1.5.5.355
Compiling Third-Party Components

For convenience, the Windows version of the SDK comes with precompiled third-party libraries. The following pages describe how to compile these components from source, e.g. if you want a newer version or cross compile the SDK.

Note
It is highly recommended to build all third-party libraries in shared object mode. Especially when building for Windows CE you must link dynamically, because wcecompat is required, which is released under the GNU LGPL and requires dynamic linking.
Warning
If you do not link OpenSSL for WindowsCE dynamically, you are violating our software license agreement (see Appendix A).

All third-party components you compile with Visual Studio have to be copied to the SDK’s folder structure.

Let’s assume you have compiled OpenSSL for Visual Studio 2008 with service pack 1 on 32 bit Windows. Then you have to create a folder named “vs2008sp1” inside the third-party folder of the SDK, similar to the already existing one containing the precompiled libraries delivered with the SDK, i.e. the new libraries have to be copied to

<SDK_INSTALL_DIR>\third-party\win32\vs2008sp1\openssl

This works similarly for other Visual Studio Versions. Here are some more examples:

  • <SDK_INSTALL_DIR>\third-party\win32\vs2008sp1\…
  • <SDK_INSTALL_DIR>\third-party\win32\vs2005sp1\…
  • <SDK_INSTALL_DIR>\third-party\win32\vs2008sp1\…
  • <SDK_INSTALL_DIR>\third-party\win64\vs2008sp1\…
  • <SDK_INSTALL_DIR>\third-party\win64\vs2010sp1\…
  • <SDK_INSTALL_DIR>\third-party\wince\vs2008sp1\…

Please see the pages below for instructions about how to compile third-party components.