Duane Ellis wrote: > 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.
While this most probably will work for all cases, it sounds quite complex and I fear that it is too complex for some people. Can we do it less complex? 1) Why having two different options for archive directory at Win and Linux --with-ftd2xx-win32-zipdir --with-ftd2xx-linux-tardir which have the same functionality behind it? 2) Why having different options for lib/inc directory at Win and Linux --with-ftd2xx-win32-incdir=<PATH_TO_DIR> --with-ftd2xx-win32-libdir=<PATH_TO_DIR> and --with-ftd2xx-linux-incdir=<PATH_TO_DIR> --with-ftd2xx-linux-libdir=<PATH_TO_FILE> which have the same functionality behind it? And why do you use PATH_TO_FILE instead of PATH_TO_DIR in Linux libdir? Why do you think that what I mentioned in previous mail -- cut -- Why not just --with-libftd2xx-dir for the directory where .tar or .zip are extracted to and where .so and .h files are located? Add path given by --with-libftd2xx-dir=<PATH> to -L and -I and everything should be fine for libftd2xx? What's about: Replace/rename --with-ftd2xx to e.g. --with-ft2232-dir then do * If --enable-ft2232_ftd2xx is enabled using --with-ft2232-dir=<PATH> results in -I<PATH> -L<PATH> where PATH is a path to tar/zip directory * If --enable-ft2232_libftdi is enabled using --with-ft2232-dir=<PATH> results in -I<PATH>/include -L<PATH>/lib where PATH is a path to the libftdi (--prefix) main install directory. In both cases, if people already moved .so/.h to some standard directories which are in include/link search path, this wouldn't hurt. -- cut -- will not work? > ================================================== > > 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. I don't think so. For open source *libftdi* on *Linux*, you can pass --prefix to configure (as I did). lib/header is then installed to <PREFIX_PATH>/include <PREFIX_PATH>/lib I.e. we need to be able to pass the <PREFIX_PATH> to OpenOCD build system and e.g. automatically append a /lib and /include subpath to it if using --enable-libftdi. The resulting path then has to be used with -I and -L. For close source *ftd2xx* and on *Linux* and set --with-ftd2xx=<PATH_TO_TAR_DIR> to the directory where you untarred it (i.e. did no install/copy), the path given is mainly fine, just that it is missing at link time (i.e. adding a -L<PATH_TO_TAR_DIR> would do it). So from my point of view (Linux having ftd2xx in tar directory and libftdi in ./configure --prefix directory) -- cut -- * If --enable-ft2232_ftd2xx is enabled using --with-ft2232-dir=<PATH> results in -I<PATH> -L<PATH> where PATH is a path to tar/zip directory * If --enable-ft2232_libftdi is enabled using --with-ft2232-dir=<PATH> results in -I<PATH>/include -L<PATH>/lib -- cut -- as mentioned above would be fine. Many thanks Dirk _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
