Freddie Chopin schrieb: > Is anyone actually checking the patches you push? Is anyone checking the > binary produced by the patches? Shouldn't there be a rc(x+1) after some > pathes were made to rc(x)? The 0.3.0 release is seriously broken and I > hope you will produce a bugfix release very soon... Just reverting this > single patch will probably do just fine. Meanwhile I'm taking the 0.3.0 > installer down from my website. > > 4\/3!!
I think, a big part of the problem is the lack of official binary builds. I have a lot of colleagues who just _use_ OpenOCD and don't want (or aren't able) to build it from source. The problem is especially important on Windows, where building it is a real PITA. OpenOCD is a direct competitor to lots of the commercial JTAG tool chains there, and if you want to convince anyone to switch, you just have to have an install.exe right on the official OpenOCD project page. If more people had tried the RCs, the problem might have shown up before the release. -- Thomas Kindler <m...@t-kindler.de> _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
