Viewer webassembly and static linking in a single webassembly

Forums: 

When using a webassembly based on sample to make a client side viewer in a commercial use, should i separate the OCCT code and use dynamic linking instead of a single webassembly file if i want to keep my additional code proprietary. Otherwise, are we in case of static linking to avoid of LGPL2?

https://dev.opencascade.org/doc/overview/html/occt_samples_webgl.html

Dmitrii Pasukhin's picture

Hello, unfortunately I can't help you from law point of view.

LGPL OCCT licence have no exceptions for WASM.

For sure, by native that platform needs static things. But that is not properly processes by OCCT license type(even  pure LGPL).

As a result you still will need to offer option to re-link your library with another OCCT version by any user wishes. And that leads to problems with your privacy of code. But if your solutions is open source, you are free to use static delivery without any limitations. For now there are only 2 workaround for private code based solution in my mind:

- Organize your web application to work with multiple libs, communicated dynamically.

- Purchase OCCT for a commercial use. OCCT offer that option and after that you are free from LGPL limitations.

Best regards, Dmitrii.

Damien Elie's picture

Thank you for your answer. I will look at dynamic loading in wasm at client side.

Regards,

Damien E.