On 2010-01-16 14:14, Thomas Kindler wrote: > Could you also provide a recent build for normal Win32?! I tried to > compile one myself a few days ago, but failed to get the libftdi stuff > working.
I was thinking about providing developement packages (whole tree [exe, scripts, dlls, pdf, info, etc.]), but without installer. The main problem is that on my webpage I don't have enough: 1. bandwith 2. quota If only OpenOCD could publish the packages on the sourceforge website... > Perhaps, you could include the STM32 patch from this message in the build? > > https://lists.berlios.de/pipermail/openocd-development/2010-January/014097.html Wasn't that committed? > I think, 0.4.0 should be delayed until there has at least been some > testing on Win32.. it seems that everyone is using your builds > exclusively, and no one is able to test (or even bisect) the RC versions. > > Messages like > > https://lists.berlios.de/pipermail/openocd-development/2010-January/014200.html > > really show the lack-of-testing-on-windows problem ;) I'll try to create a packages for testing and post them - for starters maybe the original 0.4.0-rc1 and the current master. > All the build tutorials I found are outdated, and/or don't use libftdi. > (hint, hint! ;) IMHO the easiest way is to have some Linux on a VirtualBox (or VMWare or whatever one likes) and crosscompile OpenOCD there... 4\/3!! _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
