AFAIK you're not correct there. If I take GPL code I only need to make source code available if I have modified the GPL'd code itself. Even in that case I only have to make available the modified code, not my entire code base. Locally we've been using GPL'd code for a while, we keep it in a seperate library and since we have modified it, the library source is available, but not the source to our entire application. --- In lpc2000@yahoogroups.com, Charles Manning <manningc2@a...> wrote: > > > > I am myself thinking of using FAT32. I found this driver (GPL) > > that already provides FAT32 read support: > > http://www.robs-projects.com/filelib.html > > I am investigating if it is possible to add write support to it. > > I'd like to remind y'all of the implications of GPL. > > In a small embedded environment (ie where you do not have OS-level > partitioning) If you use code under GPL, then you will need to make the rest > of your code freely available if you distribute any product that contains > this code. >
Message
Re: MMC DOS FAT16 filesystem source available --> GPL implications
2005-11-17 by seangra
Attachments
- No local attachments were found for this message.