Duane Ellis wrote: > We've talked about it but have not done it. > > I propose: > > When Beagle board is reasonably fully supported - we declare Version 1.0. > > Sound like a plan?
For 1.0 I'd like to have proper handling of --with-ftd2xx path: https://lists.berlios.de/pipermail/openocd-development/2008-October/003341.html There are two issues here: 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 :( 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. Ideas? Proposals? Thanks Dirk _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
