Zac Bowling wrote:
Part of it was licensing, since LPGL, GPL, and MLP code is hard to use with embeddable projects when there is no way to dynamically link in many embedded OSs' (everything is compiled together including OS and applications) and then our customers would not really have a way to load their customized versions of the code on to the device as required under the LGPL.
I think you misunderstand the MPL terms. The MPL is laxer in this regard than the LGPL. Firstly, it is quite happy about MPL code being linked statically with proprietary code. Secondly, it requires that the source accompany the binaries, but it does not require that you be able to replace parts of the binaries with new versions compiled with the source. So the MPL would be fine for the scenario you speak of.
The tri-license allows you to choose which of the three licences you are going to follow. So you can choose the MPL, and ignore the LGPL and GPL parts for your purposes.
If you have questions about the Mozilla licensing policy, the newsgroup mozilla.legal is the place to ask.
Gerv _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
