2009/6/21 Zach Welch <z...@superlucidity.net> > On Sun, 2009-06-21 at 13:20 -0700, David Brownell wrote: > > On Sunday 21 June 2009, Audrius Urmanavičius wrote: > > > I can also second Xiaofan, who offers distribution of .zip file with > > > Cygwin building environment set up, probably with shell script that > > > does `./bootstrap`, `./configure --with-ftd2xx-blahblah` and `make` > > > there, so that Windows users with (almost) no linux experience could > > > build openocd themselves in minutes. > > > > I can't see any particular issue with such a "build kit". > > Of course it shouldn't include binaries of any kind. > > > > It should however be exactly equivalent to carefully > > written build instructions that include fetching the > > source (maybe both "release 0.2.0" or "SVN-head" options) > > and libraries. > > Finally!! Someone came up with one of the legal workarounds! > > A build script can be distributed that automatically fetches every > single component (including the compilers, if necessary) and builds all > of the source code from scratch. > > This is simply a matter of doing the work, but I have done this for past > projects for exactly these same reasons. This may seem like extra work, > but the resulting distribution complies with the terms of the GPL. > > If we had fully modular drivers, it would even be possible to distribute > a build kit that compiles _only_ the FTD2XX driver, which can be > installed into OpenOCD's (forthcoming) driver module directory. > > All someone need do is produce a DLL that is called FTD2XX and implements (or plans to implement) all the interfaces that OpenOCD uses and release it under LGPL. The interfaces can all return failure for now. There would be no problem whatsoever releasing a binary linked against such a 'replacement' DLL... If the user choses to delete the replacement DLL and use FTDI's version, that's their choice.
Orin.
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
