libftdi Archives

Subject: Re: libftdi 1.5 Windows MinGW binary

From: Xiaofan Chen <xiaofanc@xxxxxxxxx>
To: libftdi@xxxxxxxxxxxxxxxxxxxxxxx
Date: Thu, 23 Jul 2020 10:12:48 +0800
On Sun, Jul 19, 2020 at 10:46 AM Xiaofan Chen <xiaofanc@xxxxxxxxx> wrote:
>
> On Sun, Jul 19, 2020 at 10:16 AM Xiaofan Chen <xiaofanc@xxxxxxxxx> wrote:
> >
> > Here is my build of Windows binaries for libftdi 1.5 release, built with 
> > MSYS2
> > distribution of MinGW. Python bindings are not built.
> >
> > URL: https://sourceforge.net/projects/picusb/files/
> > File name: libftdi1-1.5_devkit_x86_x64_19July2020.zip
> >
> > For users of MSYS2, you can always wait for the official binaries
> > with MSYS2 distribution.
>
> BTW, I can build python bindings as well but I am not so sure
> how well it works. I have built the python bindings for
> Python 2.7 32bit and Python 3.8 32bit/64bit.
>
> Still you may want to try more matured Python bindings
> like pyftdi (using libusb only and not libftdi) or pylibftdi.


Interestingly, the following libftdi binaries got the most download.

libftdi1-1.4git_devkit_x86_x64_14June2018.zip --2517
libftdi1-1.1_devkit_x86_x64_21Feb2014.zip -- 2723
libftdi1-1.0_devkit_mingw32_17Feb2013.zip -- 5115

The 1.0 binary is the most popular, probably because of the
following two website.
https://learn.adafruit.com/adafruit-ft232h-breakout/windows-setup
http://embedded-funk.net/running-libftdi-under-windows/

On the other hand, Adafruit has moved to use pyftdi based blinka,
no longer based on libftdi python bindings.
https://github.com/adafruit/Adafruit_Blinka

pyftdi does not depend on libftdi, rather it depends on pyusb.

FYI, pyusb has a new developer and I am also one of the admins
helping out on the support side.
https://github.com/pyusb/pyusb

pyftdi: based on pyusb and pyserial
https://github.com/eblot/pyftdi

pylibftdi: based on libftdi
https://github.com/codedstructure/pylibftdi

-- 
Xiaofan

--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx   

Current Thread