<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">as for static linking, you can with MPL (we have not done anything in the build system to support this in a sane way, but patches welcome), but be aware that there is LGPL dependencies as well, so you need to think of this when doing static linking and how that effects your distribution requirements. For the MPL code, linking shouldn't be an issue.<div><br></div><div>DISCLAIMER: I am not a lawyer, these are my opinions only, if you have legal questions, you should ask a lawyer.</div><div><br></div><div>Mike</div><div><br><div><div>On Nov 20, 2010, at 2:24 PM, raul2r2 raul wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">Hi...<div> I'm thinking in developing a new module for Freeswitch for commercial use and distribution. It would be a new end point module based in a propietary binary protocol. And here the problem raise, because I'm a bit confusing about MPL license and its implications. Would this module be considered as a derivate work?. </div>
<div> If it's considered as a derivate work, is it any kind of commercial license for freeswitch?.</div><div> and the last question, if any of this is possible, could I statically link Freeswitch core or some of its modules in my application if I don't modify its source code?.</div>
<div>Regards,</div></span>
_______________________________________________<br>FreeSWITCH-dev mailing list<br><a href="mailto:FreeSWITCH-dev@lists.freeswitch.org">FreeSWITCH-dev@lists.freeswitch.org</a><br>http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev<br>UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev<br>http://www.freeswitch.org<br></blockquote></div><br></div></body></html>