On 05/02/15 08:09, Paul Fertser wrote: > On Wed, Feb 04, 2015 at 10:44:47PM -0800, Pink Boy wrote: >>> Well, so far this is wishful thinking, currently the procedure is quite >>> complicated, especially the libraries. >> >> That says not so nice things about the codebase and build system. > > MSYS2 is able to build OpenOCD just fine, without any tweaks and > tricks. So if you want to use OpenOCD on windows, just install MSYS2. >
It is a good thing that MSYS2 has current OpenOCD builds - but it is not enough. In particular, as far as I can see you get OpenOCD from MSYS2 by installing the main MSYS2 system and then downloading OpenOCD - there is no way to install /just/ OpenOCD. For good reasons and bad reasons, users may want to install just OpenOCD and not all of MSYS2. I can fully appreciate that the OpenOCD developers prefer that people use either their distro's repositories (with MSYS2 being the "repository" for Windows), or to download the source and compile it themselves. But in doing so, you are /dramatically/ limiting your potential user base - probably by an order of magnitude. I would think it is a good thing to spread the use of OpenOCD - the more people that use it, the more support you will get from the makers of chips and debugger hardware. I can also see that there is the downside of perhaps more support questions. But with the situation at the moment, OpenOCD is pretty much a Linux-only project. Windows users need binaries - they need to be able to download an installation file from the OpenOCD website and install it. You can argue that "MSYS2 is better" or "all developers should be able to compile the code" until you are blue in the face - reality is that Windows users need a binary installation file. And so that they are confident that it is the real thing - up-to-date and free of malware - they need it from the www.openocd.org website. 98% of the work for this is done - all that's needed is a bit of website change and an attitude change. Freddie has done the work of building and archiving the binaries, both the stable versions and the development versions. Under the "Download" section of the www.openocd.org website, put links to the stable and development sections. Then there will be official binaries for OpenOCD for windows, instead of just "some site that google found". And there would be no need for Liviu or anyone else to make new pseudo-official binaries, as OpenOCD would have /real/ official binaries. A little note about MSYS2 with a link would be useful too - having it clearly on the website rather than just mentioning it on mailing lists makes all the difference. Best regards, David > If you know of any specific issues with regard to the OpenOCD's > codebase and build system, please report a bug. > ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
