Notice: MediaWiki has been updated. Report any rough edges to

Getting Started Windows

From OpenKinect
Revision as of 21:50, 20 December 2010 by Angelo (talk | contribs) (Building the Instructions)
Jump to: navigation, search

Kinect Binaries

Binaries for Kinect Drivers and Demo

Binaries and source of the driver prototype can be downloaded here. Step by step directions for installing the Kinect binaries and running the demo on Windows 7 can be found here.

Building Kinect Drivers from Source


Download these and install them somwhere:

Driver installation

There are two parts to libfreenect -- the low-level libusb-based device driver and libfreenect, the library that talks to the driver. You only need to install the driver once.

Plug in your Kinect. The Xbox NUI Motor loads first. Cancel any dialog that searches for drivers and open the Windows Device Manager. Find the Motor device, right click, and press "update device drivers" and manually browse for the location. Select the /platform/windows/inf folder within the libfreenect folders. After the Motor is installed, the Xbox NUI Camera and Xbox NUI Audio will connect and you can repeat the same thing for those drivers.

Building the Instructions


In the following, the process in order to create the drivers for Kinect in Windows and to run the example program.

  • Step 1: Download CMAKE (Cross-Platform Make) and make sure you have a working C compiler (example Visual Studio 2010 or MinGW)
  • Step 2: Download the the master branch and all the Dependencies
  • Step 3: Run CMake-gui and point to the root directory where /src, /examples, etc. are children (where it has the first CMakeLists.txt)
  • Step 4: Use the configure option, select your C complier and let it run. It will point out several mistakes that will be presented as red in the CMake Gui. You must correct these problems. For the libfreenect header you must point at c/include, for USB header c/dependencies/include and so on...[NOTE: For now only select the EXAMPLES and C_SYNC build options. The others such as FAKENECT have not been updated for Visual Studio yet.]
  • Step 5: Finally accomplish configure and generate files (CMake-> configure, CMake-> generate). When it has errors then update the missing folders to the folders of the dependencies. The *_LIBRARY variables need to point to actual .lib files not a folder. INCLUDE variables need to point to the appropriate include directories. You might need to check the advanced checkbox to access some variables.
  • Step 6: After you can successfully generate the projects, open libfreenect.sln in Visual Studio and build the project.