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

Difference between revisions of "Getting Started Windows"

From OpenKinect
Jump to: navigation, search
(Updated instructions)
Line 1: Line 1:
Getting Started in Windows
+
=== Dependencies ===
 +
Download these and install them somwhere:
  
For windows users there is a Binary available here
+
http://sourceforge.net/apps/trac/libusb-win32/wiki
http://blokmodular.com/dev/Kinect-v14-withsource.zip (the v14 demo is the last to use "simple gl".)
 
http://blokmodular.com/dev/Kinect-v15-withsource.zip (warning: the v15 demo is rather opengl-heavy.)
 
  
[http://img709.imageshack.us/img709/1444/screenvfi.jpg]
+
ftp://sourceware.org/pub/pthreads-win32/dll-latest
  
In the following, the process in order to create the drivers for Kinect in Windows and to run the example servo moving program will be presented.
+
http://www.xmission.com/~nate/glut.html
  
The guidelines where first given by the user Majorityyy, who I thank!
+
=== Driver installation ===
  
Step 1: Download CMAKE (Cross-Platform Make) and make sure you have a working C compiler (example MinGW)
+
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.
  
Step 2: Download the the master branch and all the Dependencies (see Issues > Pull Requests)
+
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.
  
You will get three folders, namely c:, csharp, platform
+
=== Building the Instructions ===
  
Step 3: Run CMake and point as source directory the aforementioned c folder (where it has the first CMakeList.txt)
+
[http://img709.imageshack.us/img709/1444/screenvfi.jpg]
  
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...
+
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 5: Finally accomplish configure and generate files (CMake-> configure, CMake-> generate)
+
Step 2: Download the the master branch and all the Dependencies
  
Ok the first part is done!
+
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 6: download Libusb-win32 and use the wizard program in order to create the drivers. You should create three drivers (Motor, Camera, Audio - not always in this order, read!). Use the install driver option inside the Libusb-win32 wizard program.
+
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...
  
Ok the second part is done!
+
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 7: open Visual Studio solution and build this project. Run Debug and you should see the tilt servo moving upwards - downwards. Ok this is a start! That is all for now.
+
Step 6: After you can successfully generate the projects, open libfreenect.sln in Visual Studio and build the project.

Revision as of 06:45, 19 December 2010

Dependencies

Download these and install them somwhere:

http://sourceforge.net/apps/trac/libusb-win32/wiki

ftp://sourceware.org/pub/pthreads-win32/dll-latest

http://www.xmission.com/~nate/glut.html

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

[1]

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...

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.