Michael Schwingen wrote: > Dick Hollenbeck wrote: > >> I am not a CMake expert, but this is a decent first draft. I believe >> it will be possible to get to a point where you can build openocd just >> with simple tools on Windows, no need for CYGWIN or even a bash shell >> script. These scripts have been tested on Linux with a variety of >> cable types. >> >> They have not been tested on Windows. Windows support may need a >> little more work, 1 hour or at most. I will ask somebody that works >> with Windows to do that for their own benefit please. I have carried >> the water pretty far here, and the Windows folks can certainly go the >> extra 3 feet. >> >> Start by installing the patch, and then reading about "out of source >> builds" in the above URL, repeated here again: >> >> >> http://www.vtk.org/Wiki/CMake_FAQ >> > Looks good to me - I never got warm with autotools, so this looks like > an improvement to me. > > I really like that the cmake-generated Makefile runs the whole build > across all directories in one make process, which works better on SMP > systems (I just did a test with "make -j" and got >20 compiler jobs > running in parallel, across all directories - traditional recursive > makefiles tend to scale bad on systems with >2 CPUs). > > Since it looks like the cmake support does not touch much of the > existing files, I think adding it to SVN should do no harm. > > cu > Michael >
There are "wanna bes" and then there are success stories. CMake is a success story. Thanks for your feedback to the list, that seems to be what is required right now. Dick _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
