[it is easier to respond to these as separate items] >> ================================================== >> >> 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 do the same sort of thing - you are not alone, and it more twisted if you use --exec-prefix I want to make one simplifying assumption. For libftdi - if you use --prefix=/some/private/path Then you must use the *SAME* private path - for OpenOCD. and it will work automatically. Otherwise the permutations get crazy. -Duane _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
