> On Tuesday 01 July 2003 15:21, Daniel Néri wrote: > > Dmitry <di...@mail.ru> writes: > > > However, copyright should be either GNU or BSD. > > > > With "GNU", I assume you mean either LGPL or GPL with some sort of > > exception? > both fine. > ~d
GPL is not fine for libraries, and LGPL is not good for embedded systems. Obviously it is up to the author to choose, but for practical use, the licence must be something like BSD. The problem is that if a library function is licenced under the GPL, then any code that uses it must also be GPL'ed. For some embedded systems, that's fine - but for many, it is not going to work. If the library is LGPL'ed, then you don't need to GPL the application code, but you do need to provide object files to the end user so that they can re-link the code with the library (unless you want to implement dynamic load-time linking on the msp...). With BSD licence, the library can be used with closed-source code. Of course, it is up to the author - some people feel so strongly that all code should be free that they don't want their code to be used in closed-source systems. The GPL is ideal for the msp development tools, but (L)GPL does not work well as a licence for embedded system libraries - most users cannot use it.
