README.Windows

   1 Building OpenOCD for Windows
   2 ----------------------------
   3
   4 You can build OpenOCD for Windows natively with either MinGW-w64/MSYS
   5 or Cygwin (plain MinGW might work with --disable-werror but is not
   6 recommended as it doesn't provide enough C99 compatibility).
   7 Alternatively, one can cross-compile it using MinGW-w64 on a *nix
   8 host. See README for the generic instructions.
   9
  10 Native MinGW-w64/MSYS compilation
  11 -----------------------------
  12
  13 As MSYS doesn't come with pkg-config pre-installed, you need to add it
  14 manually. The easiest way to do that is to download pkg-config-lite
  15 from:
  16
  17   http://sourceforge.net/projects/pkgconfiglite/
  18
  19 Then simply unzip the archive to the root directory of your MinGW-w64
  20 installation.
  21
  22 USB adapters
  23 ------------
  24
  25 You usually need to have WinUSB.sys (or libusbK.sys) driver installed
  26 for a USB-based adapter. Some vendor software (e.g. for ST-LINKv2)
  27 does it on its own. For the other cases the easiest way to assign
  28 WinUSB to a device is to use the latest Zadig installer:
  29
  30   http://zadig.akeo.ie
  31
  32 For the old drivers that use libusb-0.1 API you might need to link
  33 against libusb-win32 headers and install the corresponding driver with
  34 Zadig.
  35
  36 If you need to use the same adapter with other applications that may
  37 require another driver, a solution for Windows Vista and above is to
  38 activate the IgnoreHWSerNum registry setting for the USB device.
  39
  40 That setting forces Windows to associate the driver per port instead of
  41 per serial number, the same behaviour as when the device does not contain
  42 a serial number. So different drivers can be installed for the adapter on
  43 different ports and you just need to plug the adapter into the correct
  44 port depending on which application to use.
  45
  46 For more information, see:
  47
  48   http://msdn.microsoft.com/en-us/library/windows/hardware/jj649944(v=vs.85).aspx
  49   http://www.ftdichip.com/Support/Knowledgebase/index.html?ignorehardwareserialnumber.htm