Øyvind Harboe wrote: > On Mon, Jun 22, 2009 at 5:47 PM, Michael > Schwingen<rincew...@discworld.dascon.de> wrote: >> Harald Kipp wrote: >>> This is easier to implement than what I suggested: Building an >>> intermediate LGPL'ed DLL which links OpenOCD with FTD2XX. >>> >> I don't see how that solves the GPL problem: as soon as the FTD2XX >> library is linked into openocd, it is not OK to distribute - having an >> intermediate do the linking does not change the legal status, IMHO - but >> IANAL. > > I'm not a GPL expert, but this still sounds like trying to circumvent the > license problem and is no different than LoadLibrary() vs. implicit > LoadLibrary().
Sorry for those convoluted language constructions. We Germans love to create complicated sentences, although they typically lead to confusion. Simple version: 1. Someone creates a dummy FTD2XX library, published under LGPL. This library does not contain any FTDI-code, just dummies which contain the same entry names, but always return errors. 2. This library can be distributed with the OpenOCD executable, enabled for FT2232 support. OpenOCD will run flawlessly, but of course not work with Turtelizer 2 or similar hardware. It will work with other adapters. 3. The user can replace this dummy with the original libraries, downloadable from FTDI's website. Now OpenOCD will work with FT2232 based adapters. Harald _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
