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 misunderstood the license of the Mozilla source code. The whole MPL/LGPL/GPL tri-licensing thing makes it so that you can use any one of the licenses of your choice to redistribute. The terms of the MPL seem unlikely to be an issue for embedding a browser.
-Eli _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
