On Thu, 2009-06-25 at 22:25 +0100, Spencer Oliver wrote:
> > > you are using the wrong calling convention if this happens.
> > > Note the WINAPI
> > 
> > Dude - you rule! That was exactly the problem - I've copied 
> > the typedef for pointers from msdn and the example used 
> > __cdecl instead of WINAPI. 
> > Changing that with your suggestion fixed the problem [;
> > 
> > Thx <:
> > 
> 
> been there many times myself!!
> 
> > I'm wondering now whether I should be doing such things... /;
> > 
> > Anyway - would such feature be accepted to OpenOCD (if fully 
> > tested and working of course)? I think that it would be a 
> > good addition, because no libraries would have to be 
> > distributed with OpenOCD releases. Now - when all interfaces 
> > are enabled - the distro should have libftdi.dll (or
> > ftd2xx.dll) and libusb0.dll - even if the end-user doesn't need them.
> > 
> 
> Personally i think it is a good addition - i am not a fan of binding dll's
> at link time.
> At least then openocd can be built for all interfaces and the user does not
> have to install
> libusb and libftdi etc.

FWIW, this will not bring GPL-compliance.  Is that the goal, or just
loadable library support?  I am in favor of this later, but I thought
you were pushing for the former.

I want to see a patch before commenting about whether or not it should
be accepted here.

Zach
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to