dirk> [snip: libftdi isn't discussed here? ]
duane> My intent is that we have a complete solution,
duane> for both systems, libftdi, and libftdi2xxx.
As I dig into this a bit more - I see the source of confusion.
So let me restate the proposed solution.
==================================================
The OPTION: "--enable-ftd2xx" - enables the FTDICHIP.com (closed source)
solution.
On *WIN32* (cygwin + Mingw)
This is the package FTDICHIP.COM supplies as a ZIP file.
If enabled, one of these two A or B must be specified.
(a) --with-ftd2xx-win32-zipdir=<PATH_TO_DIR>
(b) --with-ftd2xx-win32-incdir=<PATH_TO_DIR> **AND**
--with-ftd2xx-win32-libdir=<PATH_TO_DIR>"
ie: (zipdir || ( incdir && libdir) )
if any of "--with-ftd2xx-linux-*" is specified the system is in ERROR
Configuration stops.
On Non-WIN32 (Linux - it runs no where else)
This is the package FTDICHIP.COM supplies as a TAR.GZ file.
If enabled, one of these two A or B must be defined:
(a) --with-ftd2xx-linux-tardir=<PATH_TO_DIR>
(b) --with-ftd2xx-linux-incdir=<PATH_TO_DIR> **AND**
--with-ftd2xx-linux-libdir=<PATH_TO_FILE>
ie: (tardir || ( incdir && libdir) )
Likewise,
If any of the "--with-ftd2xx-win32-*" options are specified - ERROR.
Configuration stops.
==================================================
The OPTION: "--enable-libftdi" - enables the intra2net.com *FREE*
(opensource) solution.
I believe, I do not know, that this solution works on both *WIN32*
and *LINUX* and other *UNIX* platforms.
As this "./configure" based, I would call it a "complete and proper"
solution
in that it should have installed it self in the proper way.
(1) configured. (2) built, and (3) installed the package.
Using the means provided by the package.
So - therefore - I believe that *NOTHING* needs to be done to support this.
(well, maybe the "-rpath" should be done... it is not being done today)
==================================================
is my assessment correct?
==================================================
**END**
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
