> nobo...@web.de wrote: > > Hi, > > > > in the sources of mspgcc there are files with LGPL, GPL (e. g. sprintf.c) and BSD license. > > As far as in know this means that (genenerally) all software done with mspgcc is under GPL > > and that's the reason why many companies refuse to use mspgcc.
And as I understand the LGPL, if you link staticly to an LGPL library, you have to release your source (as GPL or LGPL) - the LGPL is designed for dynamic libraries linked to closed source, which is fine for pc's and other "big" systems. For embedded systems (assuming you don't want to open-source your app), you have to stick to BSD or modified (L)GPL code, as used by the mspgcc library. > > that's just not true. read the license in the file again. it clearly > says in the last paragraph: > > """ > As a special exception, if you link this library with files > compiled with a GNU compiler to produce an executable, this does not > cause the resulting executable to be covered by the GNU General Public > License. This exception does not however invalidate any other reasons > why the executable file might be covered by the GNU General Public > License. """ > > > Would it be possible to throw out the files without LGPL and replace them by LGPL file and to > > assure that mspgcc is purely LGPL or a license with suits better for microcontroller software? > > it would not hurt to have the same license for all files. but if you > throw out a file you have to replace them with something else, and who > writes that source? > There are also good reasons for using the modified GPL - it gives the library writers almost all of the advantages of the GPL, and users almost all the advantages of BSD-style licensing. What would be very useful would be if the FSF formulated a standard EGPL for embedded use, covering this situation and saving programmers from having to mess with the legal stuff. > one thing that could be considered tough, is the use of the avr libc. is > more complete than ours and is licensed under a BSD like license: > http://www.nongnu.org/avr-libc/ > I would guess there could be a lot of advantages in working with the avrgcc people, both for the library, tools, and documentation. There are plenty of differences between the chips (the mps430 is C-friendly, while the AVR is merely IAR-friendly), but combining resources might be fruitful. David > chris > > > ------------------------------------------------------- > This SF.Net email is sponsored by: InterSystems CACHE > FREE OODBMS DOWNLOAD - A multidimensional database that combines > robust object and relational technologies, making it a perfect match > for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 > _______________________________________________ > Mspgcc-users mailing list > Mspgcc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mspgcc-users > > >
