Rick Altherr wrote: > > On Dec 16, 2008, at 11:45 PM, Dirk Behme wrote: > >> 1. Path given with --with-ftd2xx is ignored at openocd's link time. I >> think we need something like adding "-L<with-ftd2xx-path>" to build >> tooling for linking. I already had a look to this, but was lost in >> Makefile generation :( >> > > Should be relatively simple in Makefile.am, but I get lost in > configure.in.
Sounds like Duane might help here: "Let me take a look at this... give me a few days" :) >> 2a) Using libftd2xx, library libftd2xx.so and ftd2xx.h are extraced to >> the same directory. This works with --with-ftd2xx=<path_to_libftd2xx> >> (assuming that we add (1) above for proper linking) >> >> 2a) Using libftdi, header and library are installed in different >> directories >> >> <path_to_libftdi>/lib/libftdi.so >> >> <path_to_libftdi>/include/ftdi.h >> >> so we have to handle --with-ftd2xx=<path_to_libftdi> slightly >> different compared to (2a). If we use libfdi, subpaths /include and >> /lib have to be appended automatically assuming we pass >> <path_to_libftdi> to --with-ftd2xx. >> > > libftdi shouldn't use the --with-ftd2xx path. It should have a --with- > libftdi since they are completely different libraries with different -- > enable options. We could a) introduce an additional --with-libftdi. Then we would have --enable-ft2232_ftd2xx --with-ftd2xx and --enable-ft2232_libftdi --with-libftdi pairs _or_ b) rename existing --with-ftd2xx to something like --lib-ft2232-path and decide based on which --enable-xxx option is set whether to append /lib and /include sub-paths (for libftdi) or not (for ftd2xx). Dirk >> Ideas? Proposals? >> >> Thanks >> >> Dirk >> >> >> >> _______________________________________________ >> Openocd-development mailing list >> [email protected] >> https://lists.berlios.de/mailman/listinfo/openocd-development > > > -- > Rick Altherr > [email protected] > > "He said he hadn't had a byte in three days. I had a short, so I split > it with him." > -- Unsigned > > > _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
