This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: ecos license question.




Basically the exception says that you can link non-GPL code with eCos code
right. So basically this is even weaker than LGPL, because
1./ You dont have to enable the user to relink you code with newer version
of eCos (by providing the object files)
2./ You can modify the behaviour of existing eCos code by adding hooks in
eCos code and calling your own proprietary functions with those hooks.

Unlike, say, the Linux Kernel, eCOS is essentially a developer's library, which you link to your applications. Because of the architecture of eCOS, giving it a strict GPL license would be the equivalent of saying under Linux that you cannot run ANY non-free software, or even write your own non-free software under eCOS, except by special permission from the copyright owner(s) of eCOS. Since executable A loading executable B is not generally considered "linking GPL code into your non-GPL program", this exception provides the same ability, using linking as a means of combining essentially separate functionality (the RTOS itself, and your application).

The GPL+X-clause allows eCOS to in fact be used as an RTOS, running (linked in, because it's the only way currently supported) a privately written application. The intent is to provide commercial developers with impetus to use (and therefore contribute back) to the eCOS core, which is to say, to provide BSPs, drivers, and functionality, plus eyes looking for bugs, and all that other good stuff.
This new license is good for eCOS development, and will ensure (in light of the departure of RedHat) the ability of consulting companies to make money by writing closed source embedded solutions (that are so vertical in use that they would not be worth contributing to open source anyways) while contributing to improving eCOS, and creating a vibrant economy around eCOS solutions. (Here's hoping.)

Warren



--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]