Dominic pisze: > How is libftdi, and more specifically OpenOCD with libftdi support build > on Windows? > > OpenOCD ft2232.o references symbols from libftdi which references > symbols from libusb0. On Linux, libftdi and libusb are shared objects > that get dynamically linked. > > You say libftdi isn't a dll? Is it a static library (.a) that gets > statically linked to the OpenOCD?
Exactly. only libusb0.dll is a dynamic library. > You further say libftdi's code _statically_ links to libusb0.dll - do > you mean it dynamically links it (since it's a dll I assume that), but > doesn't dynamically load it at runtime (via LoadLibrary)? I'm not a pro, so I used wrong words - again that's exactly what you say. An executable compiled only for ft2232 with libftdi fails to start when there is no libusb0.dll somewhere in the system. Everything would be easier if libftdi would be a dll <: Now I'd have to change and recompile libftdi <: 4\/3!! _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
