3 ms·
I'd love to make use of this in various open source projects but as far as I know the Mozilla Public Licence has the same problem as LGPL if you ever want to bu
by andybak 6y ago
I'd love to make use of this in various open source projects but as far as I know the Mozilla Public Licence has the same problem as LGPL if you ever want to build for Android or iOS.
You can't mingle MPL/LGPL code with non-copyleft code unless it compiles to a separate binary.
And on iOS/Android - you're forced to have a single signed binary for distribution on the official stores.
Have I misunderstood? I would like to use it in conjunction with Apache licenced code. It feels like I'd be complying with the spirit but not the letter of the licence.
- mkeeter 6y agoCheck out Q8/9/10 in the MPL FAQ: https://www.mozilla.org/en-US/MPL/2.0/FAQ/ https://www.mozilla.org/en-US/MPL/2.0/FAQ/ I don't believe the MPL requires the ability to re-link; this is one of the reasons I chose it over the LGPL. (My intentions are to promote development of the libfive by require changes to the library itself to be shared, while not limiting commercial use / distribution / embedding into a larger application; there is at least one commercial CAD company using libfive as a component in their application)
- andybak 6y agoThat's great news. I can think of another project using LGPL but (I suspect) with the same intention as you. I will spread the word the MPL might be a better fit.