📄 ecos-licensing.html
字号:
<!-- Copyright (C) 2003 Red Hat, Inc. --><!-- This material may be distributed only subject to the terms --><!-- and conditions set forth in the Open Publication License, v1.0 --><!-- or later (the latest version is presently available at --><!-- http://www.opencontent.org/openpub/). --><!-- Distribution of the work or derivative of the work in any --><!-- standard (paper) book form is prohibited unless prior --><!-- permission is obtained from the copyright holder. --><HTML><HEAD><TITLE>eCos Licence Overview</TITLE><meta name="MSSmartTagsPreventParsing" content="TRUE"><METANAME="GENERATOR"CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+"><LINKREL="HOME"TITLE="eCos User Guide"HREF="ecos-user-guide.html"><LINKREL="UP"TITLE="Introduction"HREF="user-guide-introduction.html"><LINKREL="PREVIOUS"TITLE="eCos Overview"HREF="ecos-overview.html"><LINKREL="NEXT"TITLE="Previous License"HREF="ecos-licensing-previous.html"></HEAD><BODYCLASS="CHAPTER"BGCOLOR="#FFFFFF"TEXT="#000000"LINK="#0000FF"VLINK="#840084"ALINK="#0000FF"><DIVCLASS="NAVHEADER"><TABLESUMMARY="Header navigation table"WIDTH="100%"BORDER="0"CELLPADDING="0"CELLSPACING="0"><TR><THCOLSPAN="3"ALIGN="center">eCos User Guide</TH></TR><TR><TDWIDTH="10%"ALIGN="left"VALIGN="bottom"><AHREF="ecos-overview.html"ACCESSKEY="P">Prev</A></TD><TDWIDTH="80%"ALIGN="center"VALIGN="bottom"></TD><TDWIDTH="10%"ALIGN="right"VALIGN="bottom"><AHREF="ecos-licensing-previous.html"ACCESSKEY="N">Next</A></TD></TR></TABLE><HRALIGN="LEFT"WIDTH="100%"></DIV><DIVCLASS="CHAPTER"><H1><ANAME="ECOS-LICENSING">Chapter 3. <SPANCLASS="PRODUCTNAME">eCos</SPAN> Licence Overview</H1><DIVCLASS="TOC"><DL><DT><B>Table of Contents</B></DT><DT><AHREF="ecos-licensing.html#ECOS-LICENSING-QNA">Questions and answers</A></DT><DT><AHREF="ecos-licensing-previous.html">Previous License</A></DT></DL></DIV><P>As of May 2002, <SPANCLASS="PRODUCTNAME">eCos</SPAN> is releasedunder a modified version of the well known <AHREF="http://www.gnu.org/copyleft/gpl.html"TARGET="_top">GNU General Public License(GPL)</A>, now making it an <AHREF="http://www.gnu.org/philosophy/license-list.html"TARGET="_top">officialGPL-compatible Free Software License</A>. An exception clause hasbeen added to the <SPANCLASS="PRODUCTNAME">eCos</SPAN> license which limitsthe circumstances in which the license applies to other code when usedin conjunction with <SPANCLASS="PRODUCTNAME">eCos</SPAN>. The exceptionclause is as follows:</P><TABLEBORDER="5"BGCOLOR="#E0E0F0"WIDTH="70%"><TR><TD><PRECLASS="PROGRAMLISTING"> As a special exception, if other files instantiate templates or use macros or inline functions from this file, or you compile this file and link it with other works to produce a work based on this file, this file does not by itself cause the resulting work to be covered by the GNU General Public License. However the source code for this file must still be made available in accordance with section (3) of the GNU General Public License. This exception does not invalidate any other reasons why a work based on this file might be covered by the GNU General Public License.</PRE></TD></TR></TABLE><P>The goal of the license is to serve the<SPANCLASS="PRODUCTNAME">eCos</SPAN> user community as a whole. It allowsall <SPANCLASS="PRODUCTNAME">eCos</SPAN> users to develop products withoutpaying anybody anything, no matter how many developers are working onthe product or how many units will be shipped. The license alsoguarantees that the <SPANCLASS="PRODUCTNAME">eCos</SPAN> source code willalways be freely available. This applies not only to the core<SPANCLASS="PRODUCTNAME">eCos</SPAN> code itself but also to any changesthat anybody makes to the core. In particular, it should prevent anycompany or individual contributing code to the system and then laterclaiming that all <SPANCLASS="PRODUCTNAME">eCos</SPAN> users are now guiltyof copyright or patent infringements and have to pay royalties. Itshould also prevent any company from making some small improvements,calling the result a completely new system, and releasing this under anew and less generous license.</P><P>The license does <SPANCLASS="emphasis"><ICLASS="EMPHASIS">not</I></SPAN> require users torelease the source code of any <SPANCLASS="emphasis"><ICLASS="EMPHASIS">applications</I></SPAN> thatare developed with <SPANCLASS="PRODUCTNAME">eCos</SPAN>. However, ifanybody makes any changes to code covered by the<SPANCLASS="PRODUCTNAME">eCos</SPAN> license, or writes new files derivedin any way from <SPANCLASS="PRODUCTNAME">eCos</SPAN> code, then we believethat the entire user community should have the opportunity to benefitfrom this. The license stipulates that these changes must be madeavailable in source code form to all recipients of binaries based onthe modified code, either by including the sources along with thebinaries you deliver (or with any device containing such binaries) orwith a written offer to supply the source code to the general publicfor three years. It is perhaps most practical for<SPANCLASS="PRODUCTNAME">eCos</SPAN> developers to make the source codeavailable online and inform those who are receiving binariescontaining <SPANCLASS="PRODUCTNAME">eCos</SPAN> code, and probably also the<SPANCLASS="PRODUCTNAME">eCos</SPAN> maintainers, about the location of thecode. See the <AHREF="http://www.gnu.org/copyleft/gpl.html"TARGET="_top">fulltext of the GPL</A> for the most authoritative definition of theobligations.</P><P>Although it is not strictly necessary to contribute the modifiedcode back to the <SPANCLASS="PRODUCTNAME">eCos</SPAN> open source project,we are always pleased to receive code contributions and hope thatdevelopers will also be keen to give back in return for what theyreceived from the <SPANCLASS="PRODUCTNAME">eCos</SPAN> project completelyfree of charge. The <SPANCLASS="PRODUCTNAME">eCos</SPAN> maintainers areresponsible for deciding whether such contributions should be appliedto the public repository. In addition, a <AHREF="http://sources.redhat.com/ecos/assign.html"TARGET="_top">copyrightassignment</A> is required for any significant changes to the core<SPANCLASS="PRODUCTNAME">eCos</SPAN> packages.</P><P>The result is a royalty-free system with minimal obligations onthe part of application developers. This has resulted in the rapiduptake of <SPANCLASS="PRODUCTNAME">eCos</SPAN>. At the same time,<SPANCLASS="PRODUCTNAME">eCos</SPAN> is fully open source with all thebenefits that implies in terms of quality and innovation. We believethat this is a winning combination.</P><DIVCLASS="SECT1"><H1CLASS="SECT1"><ANAME="ECOS-LICENSING-QNA">Questions and answers</H1><P>The following queries provide some clarification as to theimplications of the <SPANCLASS="PRODUCTNAME">eCos</SPAN> license. They donot consititute part of the legal meaning of the license.</P><P><SPANCLASS="emphasis"><ICLASS="EMPHASIS">Q.</I></SPAN> What is the effect of the<SPANCLASS="PRODUCTNAME">eCos</SPAN> license?</P><P><SPANCLASS="emphasis"><ICLASS="EMPHASIS">A.</I></SPAN> In the simplest terms, when youdistribute anything containing <SPANCLASS="PRODUCTNAME">eCos</SPAN> code,you must make the source code to <SPANCLASS="PRODUCTNAME">eCos</SPAN>available under the terms of the GPL.</P><P><SPANCLASS="emphasis"><ICLASS="EMPHASIS">Q.</I></SPAN> What if I make changes to<SPANCLASS="PRODUCTNAME">eCos</SPAN>, or write new code based on<SPANCLASS="PRODUCTNAME">eCos</SPAN> code?</P><P><SPANCLASS="emphasis"><ICLASS="EMPHASIS">A.</I></SPAN> Then you must make those changesavailable as well.</P><P><SPANCLASS="emphasis"><ICLASS="EMPHASIS">Q.</I></SPAN> Do I have to distribute the sourcecode to my application? Isn't the GPL "viral"?</P><P><SPANCLASS="emphasis"><ICLASS="EMPHASIS">A.</I></SPAN> You do not have to distribute anycode under the terms of the GPL other than<SPANCLASS="PRODUCTNAME">eCos</SPAN> code or code derived from<SPANCLASS="PRODUCTNAME">eCos</SPAN>. For example, if you write a HAL portbased on copying an existing <SPANCLASS="PRODUCTNAME">eCos</SPAN> HAL inany way, you must make the source code available with thebinary. However you would not need to make available any other code,such as the code of a wholly separate application linked with<SPANCLASS="PRODUCTNAME">eCos</SPAN>.</P><P><SPANCLASS="emphasis"><ICLASS="EMPHASIS">Q.</I></SPAN> I would rather stick with theRHEPL code, but I updated my anonymous CVS checkout.</P><P><SPANCLASS="emphasis"><ICLASS="EMPHASIS">A.</I></SPAN> You can check out the finalversion of anonymous CVS before the license change using the CVS tag<TTCLASS="LITERAL">last-rhepl</TT>. See <AHREF="http://sources.redhat.com/ecos/anoncvs.html"TARGET="_top">the anonymous CVSaccess page</A>for details.</P></DIV></DIV><DIVCLASS="NAVFOOTER"><HRALIGN="LEFT"WIDTH="100%"><TABLESUMMARY="Footer navigation table"WIDTH="100%"BORDER="0"CELLPADDING="0"CELLSPACING="0"><TR><TDWIDTH="33%"ALIGN="left"VALIGN="top"><AHREF="ecos-overview.html"ACCESSKEY="P">Prev</A></TD><TDWIDTH="34%"ALIGN="center"VALIGN="top"><AHREF="ecos-user-guide.html"ACCESSKEY="H">Home</A></TD><TDWIDTH="33%"ALIGN="right"VALIGN="top"><AHREF="ecos-licensing-previous.html"ACCESSKEY="N">Next</A></TD></TR><TR><TDWIDTH="33%"ALIGN="left"VALIGN="top"><SPANCLASS="PRODUCTNAME">eCos</SPAN> Overview</TD><TDWIDTH="34%"ALIGN="center"VALIGN="top"><AHREF="user-guide-introduction.html"ACCESSKEY="U">Up</A></TD><TDWIDTH="33%"ALIGN="right"VALIGN="top">Previous License</TD></TR></TABLE></DIV></BODY></HTML>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -