On Sunday 08 November 2009, Thomas Kindler wrote:
> After three hours of fiddling around, I found out, that the windows
> drivers have to be _installed_ on the system - The script will fail on a
> system that hasn't seen the dongle. OpenOCD compiles fine after
> commenting out the configure check.
Curious. Seems like a bug in the D2XX library ... there's
no reason that a FT_GetLibraryVersion() call should fail
if the driver isn't installed. A failure should only show
up when trying to open a device that's not there
> I think, the actual program run should be removed from the configure
> script entirely. At least, it should have more debugging output.
Patches accepted; a new message would be easy.
I suspect the reason for the "run" step is likely because
folk ran into installation problems which that prevents.
It'd be important to know why it's there before removing it.
Those checks seem to have been added by this patch:
commit f7274784a22e975dbab6a8b24770b652a813e64d
Author: duane <du...@b42882b7-edfa-0310-969c-e2dbd0fdcd60>
Date: Sat Dec 27 01:15:50 2008 +0000
Build Permutations with ftd2xx and libftdi addressed.
Also added a new se of regression makefiles to build
openocd in multiple ways
Which was svn1275, predating the 0.1.0 release.
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
