X-Git-Url: https://review.openocd.org/gitweb?p=openocd.git;a=blobdiff_plain;f=README.Win32;h=6c690c9cdcb3a4a2527353355b9ae7e4b315f551;hp=42b3f139f41af551324131f38a7f26dae22a5bea;hb=1163435e19f316a4a97fd33f1467f5c1684db654;hpb=ff5170a979221ed5c3962c716f63a5ef3c83d9d5 diff --git a/README.Win32 b/README.Win32 index 42b3f139f4..6c690c9cdc 100644 --- a/README.Win32 +++ b/README.Win32 @@ -27,8 +27,8 @@ based JTAG debuggers. http://sourceforge.net/projects/libusb-win32/ -You need to download the libusb-win32-device-bin-0.1.12.2.tar.gz -package. Extract this file into a temp directory. +You need to download the libusb-win32-device-bin-0.1.12.2.tar.gz +package. Extract this file into a temp directory. Copy the file libusb-win32-device-bin-0.1.12.2\include\usb.h to your MinGW include directory. @@ -40,7 +40,8 @@ Take note that different Linux distributions often have different MinGW installation directory. Some of them also put the library and include into a separate sys-root directory. -If there is a new svn version of libusb-win32, you can build it as well. +When the libusb-win32 repository is more current than its release code, +you could build that instead. These are the instruction from the libusb-win32 Makefile: @@ -58,10 +59,10 @@ released source tarball or the git tree. If you are using the git tree, the following are the instructions from README.mingw. You will need to have the cmake utility installed. -- Edit Toolchain-mingw32.cmake to point to the correct MinGW +- Edit Toolchain-mingw32.cmake to point to the correct MinGW installation. - Create a build directory like "mkdir build-win32", e.g in ../libftdi/ -- cd into that directory and run +- cd into that directory and run "cmake -DCMAKE_TOOLCHAIN_FILE=../Toolchain-mingw32.cmake .." - Copy src/ftdi.h to your MinGW include directory. - Copy build-win32/src/*.a to your MinGW lib directory. @@ -93,5 +94,5 @@ To use ftd2xx: --with-ftd2xx-win32-zipdir=/path/to/libftd2xx-win32 \ ... other options ... -If you are using the SVN repository, see the README file for additional +If you are using the GIT repository, see the README file for additional instructions about configuring and building OpenOCD.