dirk> 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?
yes, you are right - I am not following the KISS principle, I seem to have mis-placed my mind. > 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? Because it is _not_exactly_ the same functionality, and the names are confusing. One option only works on linux, the other option only works on windows. The *names* force people to think -I hope. Also - while the ".h" file is the same, the library filenames are different and that becomes messy. ====== About the "-incdir" and "-libdir" I think I will drop those as a KISS principle unless somebody needs them. ====== So we support: --with-ftd2xx-win32-zipdir --with-ftd2xx-linux-tardir And - libftdi (opensource) via 2 methods: 1) "installed in a standard place" 2) or already present in the "--prefix" parameter given to openocd's configure command. The "libftdi" approach might be usable for packages like "winarm" - that - build an entire tool kit from multiple parts - and distribute a binary package of some sort. I don't want to get into permutation hell. (Which is what I was doing to myself) -Duane. _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
