Thanks for pointing out the system32 thing. I forgot about that. I'm an
embedded developer, I don't do things like DLL's ;-)
Bit confused here, what do you mean with "BOTH libraries"
-------- Original Message --------
Subject: [Openocd-development] Creative summary of options for OpenOCD
distros
From: Freddie Chopin <freddie_cho...@op.pl>
To: openocd-development <openocd-development@lists.berlios.de>
Date: Thu Jun 25 2009 00:20:53 GMT+0200 (Romance Standard Time)
Ronald Vanschoren pisze:
Link-kit is definitely better then build-kit, but what are we doing
here? Dynamic linking is also a "link-kit". In my interpretation of GPL,
there is nothing illegal to distributing an OpenOCD binary that _CAN_
link to FTD2XX but doesn't require it. We (OpenOCD community) would not
distribute FTD2XX ourselves, but point users to the FTDI download page
and say "if you download the DLL and put it in the OpenOCD directory,
something magic could happen". I'm assuming here it's not legal to
distribute FTD2xx, I don't know about that as I don't know what license
it's available under.
This is not required, because when one installs the drivers for FTDI
based device, the ftd2xx.dll is automatically copied from the "driver
package" to windows/system32 folder. The library (dll) just has to be
"somewhere" where it can be reached via PATH variable. So if one has
FT2232 based dongle, one has the library somewhere on the system - no
additional downloading and copying that anywhere is required.
BTW in such scenario it would be best to modify the code so that it
could use BOTH libraries, selectable somehow during runtime
(automatically or manually).
4\/3!!
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
|
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
