GPL ,LGPL ,and our application
Tim at Rikers.org
Fri Sep 6 00:34:50 EDT 2002
This is the wrong list for this question. I've copied the uClibc list on
my reply that would be a better place to ask.
As noted in the COPYING.LIB:
uClibc is under the LGPL which states:
5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library". Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.
So your application can link to uClibc and not be required to be open
source. This would not be true if the GPL license was used, but is true
under the LGPL.
> we want to make a product using Coldfire5272 with uclinux, but we meet a license problem.
> according to GPL/LGPL we need to open our application source code if the application program are static linked with uc-libc.
> I want to know how to avoid to open application source code , otherwise the others can clone our product without any problem . Some other company using uclinux in their product may face same problem before so I want to know how them handle this?
> thanks a lot!
Tim Riker - http://rikers.org/ - TimR at Debian.org
Lineo CTO - Tim at Lineo.com - http://www.Lineo.com/
BZFlag maintainer - http://BZFlag.org/ - for fun!
More information about the linux-mtd