[ECOS] ecos license question.

Shannon Holland holland@loser.net
Thu Jan 16 05:43:00 GMT 2003

On Wednesday, January 15, 2003, at 06:19  AM, Jonathan Larmour wrote:

> The only code you can keep to yourself are files containing no eCos 
> code in part or full.

As I'm moving towards developing a commercial application, I'm also 
interested in making sure I fully understand this.

So my own code (which might include ecos header files and call ecos) is 
covered by whatever license I choose to give it. If I make changes to 
ecos itself, I need to make them public (and have absolutely no problem 
with doing so!). If I copy some section of ecos code and put it in my 
own, I need to make that part public.

As far as making code public, is giving my ecos changes back to the ecos 
source tree/development group adequate or do I need to make the source 
files available separately as well?


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

More information about the Ecos-discuss mailing list