Hello,

On Sun, Feb 01, 2015 at 11:19:11AM +0800, Xiaofan Chen wrote:
> Personally I do not use MSYS2 and have no intention of using it
> since I only deal with a few projects and I do not have the need
> for MSYS2. But I remember Pete from the libusb project seems to
> like it.

My mail wasn't actually directed to you personally as I do no think
you're actively using OpenOCD on windows to get real job done. But I
know for sure there're plenty of people (I guess thousands) who
actually depend on OpenOCD on windows in their dayjob and hobby
activities, and I am asking them to contribute here.

I do not understand why would anyone use windows at all without
something sane to manage packages. mingw-get used to be the thing, but
it makes little sense now. And MSYS2 is the only active project
providing reasonable experience.

> I think there is no real work on the libusb-compat side to make it
> as easy to build as the regular libusb. You may want to try again
> in the libusb mailing list to see the response.

My point is that the work is already done and libusb-compat is already
buildable on windows natively with just a small patch, you can just
take the patch, discuss and merge upstream, I think. And libusb-compat
might be useful for plenty of projects as they do not depend on
non-standard additions to libusb-0.1 API.

> > There's one problem left though, where the OpenOCD project will need
> > your hand: currently MSYS2 is lacking a PKGBUILD for
> > libftdi1. Creating one should be straightforward considering libftdi
> > has no obscure dependencies and uses CMake in a regular way. So
> > please, create one, test and push upstream to the fine MSYS2 devs.
> 
> That depends on what you mean by packaging libftdi1, it can be
> the worst to package under Windows if you want to build all the
> parts of it (even though it is easy to do under Linux). 

The point of using MSYS2 is that it should be as easy to build complex
software (e.g. libav or Qt) on windows as it is on GNU/Linux. In our
particular usecase only the C library is needed, of course. But I can
imagine how libftdi users would be happy to have C++ and Python
bindings trivially available on Windows if someone does the packaging.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

------------------------------------------------------------------------------
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

Reply via email to