Quantcast

libftdi1-1.2 and libftdi1 git master Windows binary for MinGW.org

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

libftdi1-1.2 and libftdi1 git master Windows binary for MinGW.org

Xiaofan Chen
I have not built Windows binary for libftdi for a while. It seems
that there are still some requests for the Windows binary.

So I first built the MinGW.org (MinGW 4.7.2, not the latest) binary.
You can download the libftdi Windows binaries here.
https://sourceforge.net/projects/picusb/files/

libusb-1.0.20 is used for the development kit. It is
recommended that you use Zadig to install WinUSB
driver for the development kit. You can also use
libusbK driver if you want to use both libftdi-0.1x
and libftdi1-1.x. Please do not use libusb-win32
device driver (libusb0.sys) since it does not work
well under libusb-1.0.20.


--
Xiaofan

--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to [hidden email]  

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: libftdi1-1.2 and libftdi1 git master Windows binary for MinGW.org

Xiaofan Chen
On Sun, Dec 13, 2015 at 12:47 PM, Xiaofan Chen <[hidden email]> wrote:

> I have not built Windows binary for libftdi for a while. It seems
> that there are still some requests for the Windows binary.
>
> So I first built the MinGW.org (MinGW 4.7.2, not the latest) binary.
> You can download the libftdi Windows binaries here.
> https://sourceforge.net/projects/picusb/files/
>
> libusb-1.0.20 is used for the development kit. It is
> recommended that you use Zadig to install WinUSB
> driver for the development kit. You can also use
> libusbK driver if you want to use both libftdi-0.1x
> and libftdi1-1.x. Please do not use libusb-win32
> device driver (libusb0.sys) since it does not work
> well under libusb-1.0.20.
>

I believe it should still work with latest MinGW.org toolchain.
If not, please let me know. I have some problems with the
later version of MinGW.org and I think it is not as stable.

The reason I use this old setup is also due to the fact I can
build everything libftdi offers (including the test program
using Boost Unit Testing Framework) under Windows. I am
lazy to build Boost again myself and the other ready-made
Boost binary seems to fail to build the test program somehow.

Tools used to build this package:
  CMake 2.8.10.2: http://www.cmake.org/
  MinGW GCC 4.7.2 : http://www.mingw.org
  Boost 1.49 (build from source): http://www.boost.org
  Python 2.7.3: http://www.python.org
  swig 2.09: http://www.swig.org/
  doxygen 1.8.3: http://www.doxygen.org/
  libconfuse 2.7: http://www.nongnu.org/confuse/
  pkg-config lite 0.28_1 :http://sourceforge.net/projects/pkgconfiglite/

Boost building reference:
  http://code-slim-jim.blogspot.sg/2012/04/boost-149-in-windows-7-using-mingw.html

The trend seems to go for MinGW-w64 project under Windows,
especially the MSYS2 distribution. I will build 32/64bit Windows
binary for MSYS2 when I have some time. I remember I can build
almost everything except the test program with MinGW-w64 (which
seems to have linking problem).


--
Xiaofan

--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to [hidden email]  

Loading...