Re: [OpenOCD-devel] Is MSYS2 going to be "Homebrew for Windows"?

[Andrew L. <cor...@gm...>]

On 12/06/2014 9:45 PM, Andrew Leech wrote:
> On 12/06/2014 7:02 pm, Xiaofan Chen wrote:
>> Once potential problem could be with libusb-compat. It is not
>> officially supported by the libusb project under Windows since
>> there is this libusb-win32 project which is still alive.
>>
>> I happen to be both the admin of libusb-win32 and libusb. Even
>> though we do not plan anything new things to libusb-win32 it still
>> enjoy very wide use and so far we do not see any need to
>> have the new libusb-compat under Windows since it
>> will not offer many advantages compared to libusb-win32.
>> In fact it can not support the full feature of libusb-win32
>> API which is a superset of libusb-0.1/libusb-compat.
>>
> I'm certainly not going to argue with you on this, I only threw the 
> libusb-compat script together today just to get openocd to compile 
> with the standard adapters enabled following the homebrew suggestions 
> for that package. I've previously used libusb-win32 on windows and I'm 
> certainly happy to push it over libusb-compat if it's still the 
> preferred libusb 0.1 layer on windows.
> The lack of official support for libusb-compat on windows makes a lot 
> of sense to me, considering it wouldn't just build for me. I did have 
> to make a small patch for it to cover some undefined things (u_int*_t 
> types and ENODATA in errno.h)
>
A minor (?) issue with libusb-win32 in this context is that it does not 
support driver compilation under mingw... which means I can't really 
make a normal build script for it to go with the libusb and openocd ones.
The scripts are pretty flexible however (basically bash scripts), and I 
could make a script that simply installs the binary distribution of 
libusb-win32 into the mingw environment such that it's available to 
openocd. I don't see that as a particularly bad option, seeing as the 
binary distributions are officially hosted on sf along with the source.

Andrew