Quote:
Originally Posted by knc1
... Can only publish object code (original or derived) as part of an application for a licensed i.MX device (the kindles are).
May not publish object code "free standing" whatever Freescale legal department thinks that is. ...
|
That sounds to me like you can publish a linked module but not linkable .o or .obj files. So it should be safe to distribute both the .exe and the RAM kernel file (especially when packaged together in a .zip file as suggested by the freescale agreement). Embedding a binary into an executable (even if encoded) could violate their "no GPL" clause, but a freestanding binary should be fine. As far as GPL cares, the RAM kernel is just data, but if embedded it could be interpreted as code.
Proprietary and GPL programs can only communicate through STDIO, as I interpret the various legal decisions. So a GUI wrapper around GPL is okay, especially if the end user downloads the GPL part separately from an authorized website or you provide it on separate media (or if the program downloads it automatically on request by the end user).
It would be best to avoid GPL altogether if using any freescale source code here, but LGPL is fine if you do not static link to it.
There is a Lawyer who frequents the parent forum (Harmon). He might give us an informed (non-binding) free opinion on this matter if asked nicely.
https://www.mobileread.com/forums/sho....php?p=2195551