License problem statically linked OPC UA Server ?
Posted: 08 Apr 2020, 12:25
I am building an OPC UA Server that is linked statically with LibXML, OpenSSL, Ua Server SDK.
This results in just one executable without any needed DLL's.
The executable will run only Windows 7,8,10 (not Windows CE)
Technically no problem, everything works fine.
What makes me curious is the following note in the documentation
Building the SDK and Third-Party Libraries/Compiling Third-Party Components :
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.
Does anyone know what's the reason for that note ?
Do I have a license problem (SDK and or Third party components) when I distribute the server as one statically linked executable ?
As mentioned above, I am NOT building for Windows CE.
This results in just one executable without any needed DLL's.
The executable will run only Windows 7,8,10 (not Windows CE)
Technically no problem, everything works fine.
What makes me curious is the following note in the documentation
Building the SDK and Third-Party Libraries/Compiling Third-Party Components :
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.
Does anyone know what's the reason for that note ?
Do I have a license problem (SDK and or Third party components) when I distribute the server as one statically linked executable ?
As mentioned above, I am NOT building for Windows CE.