Thu, 10/10/2013 - 19:38
Hi All,
Can I link OCC with my app statically, without opening the source of my app? I would love to contribute to OCCs development, however, I don't wan't to open my applications source code.
Istvan
Collaborative development portal
Tue, 10/29/2013 - 16:17
For not opening the source code of your application, you must use OCCT without modifying the libraries, that is, dynamically link your application to OCCT through the provided shared library (.so or .dll). Indeed, linking statically requires to provide either your source code or your linkable object files.
Daniel
Tue, 10/29/2013 - 16:23
Hi Daniel,
Sorry - this is incorrect statement. Nothing in the current public license requires either of these conditions - using unmodified version or dynamic linking.
There are currently no conditions in the license that would trigger disclosing the source code of the user application.
"For greater certainty, it is expressly understood that You may freely create Derivative Programs (without any obligation to publish such Derivative Program) and distribute same as a single product. In such case, You must ensure that all the requirements of this License are fulfilled for the Software or any portion thereof."
Thank you,
Roman
Tue, 10/29/2013 - 20:39
You are absolutely right, thank you for correcting me, Roman.
Indeed - I'm probably victim of a Freudian slip - I've described the requirement of LGPL. This is where our license differs from LGPL. So, Istvan, the answer to your question is yes: statically linking your application to OCCT does not require to open your source code.
Daniel
Tue, 10/29/2013 - 23:57
Thanks for the confirmation, Daniel.
Static linking indeed, by default, triggers the derivative work to become LGPL'ed. There is also vague area regarding templates and inline functions in LGPL. That is why some libraries (like Qt) come with explicit extensions clarifying that such cases do not trigger LGPL.
As for modifications, LGPL requires that modifications must be made available under the LGPL license on a free basis. The derivative work, if linked dynamically, still does not need to be LGPL'ed. That is, the library remains LGPLed, while the client's code - not necessarily.
Roman
Wed, 10/30/2013 - 17:43
Great, thanks, then soon I will be an active contributor to OpenCASCADE. :)