On Fri, 2009-05-01 at 20:25 -0500, Dick Hollenbeck wrote: > Fixes some problems. Has worked on OS2, Linux, Windows, Cygwin now. > > It generates both openocd executable and also now a libopen-ocd.so file > for folks wanting to make a shared object / DLL. That would be me. I > think I want to call it from Java now. So I will probably adding a SWIG > file separately that only gets linked in to the DLL/DSO, not the > executable for folks not interested.
Excellent. I can push the autotools in this direction too. Does anyone else here consider themselves responsible for OpenOCD's autotools support, or should I just help myself and take charge? > I will be adding the ability to generate the windows version from Linux > soon. That is simply a CMake toolkit file that will be forth coming. I will eventually need to produce a MinGW32 build myself as well, but I have done that with autotools in the past. > I have to support a Windows customer using a Cortex M3 device. I want > him to use code I can modify, and I don't want to have to boot Windows > to build it. I think this shows that CMake deserves to be put in ASAP. It will have commercial support, and it does not get much better than that. Cheers, Zach _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
