Duane Ellis wrote: > [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
Copy from the other mail: "I think I will drop those as a KISS principle unless somebody needs them. " I would apply this to --exec-prefix, too. I would be totally happy if we support libftdi installed with --prefix, only, for the moment. > 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. It would help if you tell _how_ to "use the *SAME* private path - for OpenOCD". Reading the other mail, I think you mean using --prefix for OpenOCD with the same path as used for libftdi build/install? > and it will work automatically. You mean with --prefix? No. Because at the moment OpenOCD totally misses -I and -L option given by --prefix: -- cut -- > mkdir install > cd install/ install> pwd ~/openocd/test/install install> cd .. > tar xfz libftdi-0.14.tar.gz > cd libftdi-0.14/ libftdi-0.14> ./configure --prefix=~/openocd/test/install libftdi-0.14> make libftdi-0.14> make install libftdi-0.14> cd .. > ls install/lib/ libftdi.a libftdi.la libftdi.so libftdi.so.1 libftdi.so.1.14.0 > ls install/include/ ftdi.h > cd trunk trunk> ./bootstrap trunk> ./configure --enable-ft2232_libftdi --prefix=~/openocd/test/install trunk> make ... if gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src -I../../src/helper -I../../src/target -g -O2 -MT ft2232.o -MD -MP -MF ".deps/ft2232.Tpo" -c -o ft2232.o ft2232.c; \ then mv -f ".deps/ft2232.Tpo" ".deps/ft2232.Po"; else rm -f ".deps/ft2232.Tpo"; exit 1; fi ft2232.c:49:18: error: ftdi.h: File or directory not found ... -- cut -- And if you "fix" this by passing -with-ftd2xx=~/openocd/test/install/include *additionally*: -- cut -- ... trunk> ./configure --enable-ft2232_libftdi -with-ftd2xx=~/openocd/test/install/include --prefix=~/openocd/test/install trunk> make ... gcc -g -O2 -o openocd openocd-main.o openocd-openocd.o ../src/xsvf/libxsvf.a ../src/target/libtarget.a ../src/jtag/libjtag.a ../src/helper/libhelper.a ../src/server/libserver.a ../src/helper/libhelper.a ../src/flash/libflash.a ../src/target/libtarget.a ../src/pld/libpld.a -lftdi -lusb -ldl /bin/ld: cannot find -lftdi -- cut -- it fails due to missing -L. > Otherwise the permutations get crazy. Sorry if I missed something, but it seems to me that you didn't mention yet why the simple --with-libftd2xx-dir proposal technically won't work? Except that it doesn't cover all cases you have in mind (what I didn't understand, yet, see other mail)? Best regards Dirk _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
