X-Git-Url: http://developer.intra2net.com/git/?p=libftdi;a=blobdiff_plain;f=README.mingw;h=771204cd495ea725a1b8e74a975b11ae5690268a;hp=3b0e5bad2c9c2491c430057f2fb1c51d2185a59e;hb=19f1452cde9bfe9da0e2830af128fae958ae877a;hpb=161206ce8c4dbb25a7660c865993bba4eb8e119b

diff --git a/README.mingw b/README.mingw
index 3b0e5ba..771204c 100644
--- a/README.mingw
+++ b/README.mingw
@@ -1,52 +1,36 @@
 * How to cross compile libftdi-1.x for Windows? *
-   1 - To cross-compile for Win32 with mingw, you need to
-       have libusb-1.0 for Windows. libusbx is a fork of libusb-1.0
-       project which has gained popularity under Windows and Linux.
-       Therefore the instruction here uses libusbx. The process to
-       use libusb-1.0 from libusb.org is similar but take note it
-       does not offer Windows binary as of Jan 09 2013.
-
-   2 - Get libusbx Windows release binary from Sourceforge.
-       http://sourceforge.net/projects/libusbx/files/releases/
-
-   3 - The release version is libusbx-1.0.14-win.7z (706.2KB)
-       as of Jan 09, 2013.
-
-   4 - Alternatively you can also build form the release source tar ball
-       or the git source tree following standard cross compile process
-
-   5 - Copy include/libusbx-1.0/libusb.h to the include directory of your
-       cross compiler, eg.,
-       /opt/cross/i386-mingw32msvc/include/
-
-   6 - Copy MinGW32/static/libusb-1.0.a and MinGW32/dll/libusb-1.0.dll.a
-       to the library directory of your cross compiler, eg.,
-       /opt/cross/i386-mingw32msvc/lib/
-
-   7 - Create a build directory like "mkdir build-win32", e.g in ../libftdi/
-
-   8 - edit Toolchain-mingw32.cmake to reflect your cross compiler location.
-
-   9 - cd into the build directory and run
-       "cmake -DCMAKE_TOOLCHAIN_FILE=../Toolchain-mingw32.cmake .."
-
-  10 - Copy src/ftdi.h to the include directory of your cross compiler,
-         eg., /opt/cross/i386-mingw32msvc/include/
-
-  11 - Copy build-win32/src/*.a to the library directory of your cross compiler,
-         eg., /opt/cross/i386-mingw32msvc/lib/
-
-
-* How to run libftdi-1.x under Windows *
-
-libusbx (or libusb-1.0) Windows backend will rely on a proper driver to run.
-Please refer to the following wiki page on the instruction of
-installation of the proper driver.
-https://github.com/libusbx/libusbx/wiki/Windows-Backend#wiki-How_to_use_libusbx_on_Windows
-
-As of Jan 09 2013, libusb-1.0 Windows backend only supports WinUSB
-and libusbx's support of libusb0.sys and libusbk.sys are considered less
-mature than WinUSB. Therefore, WinUSB driver installation using Zadig
+   1 - Prepare a pkg-config wrapper according to
+       https://www.flameeyes.eu/autotools-mythbuster/pkgconfig/cross-compiling.html ,
+       additionally export PKG_CONFIG_ALLOW_SYSTEM_CFLAGS and
+       PKG_CONFIG_ALLOW_SYSTEM_LIBS.
+   2 - Write a CMake toolchain file according to
+       http://www.vtk.org/Wiki/CmakeMingw . Change the path to your future sysroot.
+   3 - Get libusb sources (either by cloning the git repo or by downloading a
+       tarball). Unpack, autogen.sh (when building from git), and configure like this:
+       ./configure --build=`./config.guess` --host=i686-w64-mingw32 \
+               --prefix=/usr --with-sysroot=$HOME/i686-w64-mingw32-root/
+   4 - run
+       make install DESTDIR=$HOME/i686-w64-mingw32-root/
+   5 - go to libftdi-1.x source directory and run
+       cmake -DCMAKE_TOOLCHAIN_FILE=~/Toolchain-mingw.cmake \
+             -DCMAKE_INSTALL_PREFIX="/usr" \
+             -DPKG_CONFIG_EXECUTABLE=`which i686-w64-mingw32-pkg-config`
+   6 - run
+       make install DESTDIR=$HOME/i686-w64-mingw32-root/
+
+* How to run libftdi 1.x under Windows *
+
+On 26-Jan-2014, libusbx and libusb project were merged with the release
+of libusb-1.0.18 and now the project is called libusb.
+
+libusb Windows backend will need to rely on a proper driver to run.
+Please refer to the following wiki page for proper driver installation.
+https://github.com/libusb/libusb/wiki/Windows#wiki-How_to_use_libusb_on_Windows
+
+As of 26-Jan-2014, libusb Windows backend supports WinUSB,
+libusb0.sys and libusbk.sys driver. However, libusb's support of
+libusb0.sys and libusbk.sys is considered to be less mature than
+WinUSB. Therefore, WinUSB driver installation using Zadig
 is recommended.
 
 Take note once you replace the original FTDI driver with WinUSB driver,