blob: 9376dd5fcb184249c0724c56832ebf2892ab9478 [file] [log] [blame]
Pete Batard75b1cf82012-05-10 16:44:30 +01001Installation Instructions for Windows
2*************************************
3
4If you are compiling for MinGW or cygwin, please refer to the INSTALL file.
5
6If you are using Microsoft Visual Studio:
7- Open the relevant solution file in /msvc:
hjelmn@cs.unm.edu1eff2202014-01-08 23:50:34 +00008 libusb.dsw for MSVC6, libusb_2005.sln for Visual Studio 2005 or 2008,
9 libusb_2010.sln for Visual Studio 2010,
10 libusb_2012.sln for Visual Studio 2012 or later,
11 libusb_wince.sln for Windows CE support in Visual Studio 2005.
Pete Batard75b1cf82012-05-10 16:44:30 +010012- If you want to debug the library, uncomment the ENABLE_DEBUG_LOGGING define
13 in msvc\config.h
14- Select your configuration and compile the project
15
16Note that if you are using Visual Studio Express, you may have to install the
17Windows SDK to be able to compile the 64 bit version of the library.
18
19If you are using the freely available Windows DDK/WDK (Driver Development Kit)
20- If you want to debug the library, uncomment the ENABLE_DEBUG_LOGGING define
21 in msvc\config.h
22- Open one of the relevant Free Build or Checked Build prompt for your target
23 platform
24- Navigate to the msvc\ directory where the ddk_build.cmd file is located, and
25 run 'ddk_build'
26- To produce a DLL rather than a static library, use: 'ddk_build DLL'
27- To produce a static library that uses LIBCMT[d] instead of MSVCRT[d] (/MT[d]
28 vs /MD[d] in Visual Studio) use: 'ddk_build /MT'
29
30Note that using the Windows DDK, it is possible to compile both the 32 and 64
31bit versions of the library.
32
Toby Gray5bdea902013-01-16 02:10:31 +000033If you are building for Windows CE then you will need the Windows CE Standard 5.00 SDK.
Pete Batard75b1cf82012-05-10 16:44:30 +010034
35Destination directories
36***********************
37
38The 32 bit binaries compiled either from Visual Studio or the DDK are placed in
39a Win32\ directory at the root of the library
40The 64 bit binaries are placed in an x64\ directory
Toby Gray5bdea902013-01-16 02:10:31 +000041Windows CE binaries are placed in one of the following directories, depending
42on the target processor: ARMV4I, MIPSII, MIPSII_FP, MIPSIV, MIPSIV_FP, SH4 or x86.
Pete Batard75b1cf82012-05-10 16:44:30 +010043
44
45Troubleshooting
46***************
47
48If the compilation process complains about missing libraries, ensure that the
49default library paths for your project points to the relevant directories.
50If needed, these libraries can be obtained by installing either the latest
51Windows SDK or the DDK (Links provided at the end of this file).
52
Toby Gray5bdea902013-01-16 02:10:31 +000053For Windows CE it is necessary to install the CE USB Kernel Wrapper driver for
hjelmn@cs.unm.edu1eff2202014-01-08 23:50:34 +000054libusb to function on a device.
Pete Batard75b1cf82012-05-10 16:44:30 +010055
56Links
57*****
58
59Additional information related to the Windows backend:
hjelmn@cs.unm.edu1eff2202014-01-08 23:50:34 +000060 http://windows.libusb.info
Pete Batard75b1cf82012-05-10 16:44:30 +010061
62Latest Windows Driver (Development) Kit (WDK):
63 http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=36a2630f-5d56-43b5-b996-7633f2ec14ff
64
65Latest Microsoft Windows SDK:
66 http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=c17ba869-9671-4330-a63e-1fd44e0e2505
Toby Gray5bdea902013-01-16 02:10:31 +000067
68Windows CE Standard 5.00 SDK:
69 http://www.microsoft.com/en-gb/download/details.aspx?id=17310
70
71Windows CE USB Kernel Wrapper Driver:
72 https://github.com/RealVNC/CEUSBKWrapper
73