forked from thp/psmoveapi
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathREADME.win32
92 lines (65 loc) · 2.92 KB
/
README.win32
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
Building and running the PS Move API on a legacy operating system
=================================================================
We usually build PS Move API for Windows on Linux via cross-compliation, as
we don't run Windows for day-to-day work. For cross-compiling the PS Move API
for Windows on Linux, you can use the following script:
contrib/cross-compile-mingw64
Please take into account that nobody has yet managed to make Bluetooth pairing
work reliably on Windows (it works reliably on both Mac OS X and Linux). If you
plan to do serious development, it's time to switch to Mac OS X or Linux. As an
alternative, you can use a Linux host for Bluetooth communcation, and export
the controller via "moved" to the Windows host. This setup has reliable pairing,
and you can still develop and build your applications in Windows if you have to.
Requirements
------------
- MinGW
http://mingw-w64.sourceforge.net/
- CMake
http://www.cmake.org/cmake/resources/software.html
- OpenCV
http://sourceforge.net/projects/opencvlibrary/files/opencv-win/
- Git
http://code.google.com/p/msysgit/
- CL Eye Driver (if you plan to use the PS Eye camera)
http://codelaboratories.com/get/cl-eye-driver/
Optional dependency:
- CLEyeSDK
http://codelaboratories.com/get/cl-eye-sdk/
IMPORTANT: Get the right MinGW version!
-> "Regular" MinGW might not be able to build the PS Move API, as we are
using some features that are only included in MinGW-W64.
-> Get "MinGW-W64" instead. Despite its name, it also works for 32-bit
systems (and you probably have to/want to build PS Move API as 32-bit
library on Windows, anyway. This is also what we use, both for cross-
compiling it on Linux, and for building it directly on Windows.
1. build and configure OpenCV with cmake
:: you may skip to build OpenCV on your own, however i had no luck
:: the binary distribution did not work on my system
cd <where you extracted opencv>
mkdir build
cd build
cmake .. -G "MinGW Makefiles"
mingw32-make
:: now go for a coffe-break
2. Get you clone of the psmoveapi
git clone git://github.com/thp/psmoveapi.git
cd psmoveapi
4. Init and update the submodules
git submodule init
git submodule update
5. make OpenCV known to your system and the cmake toolchain
set OpenCV_DIR=<the path where you extracted opencv>
set PATH=%PATH%;%OpenCV_DIR%\build\bin
You can also build opencv in a folder "opencv" inside the
source directory (opencv/build/install) and then use the
CMake option "PSMOVE_USE_LOCAL_OPENCV" to link against
OpenCV statically from this checkout / build directory.
7. prepare a new build with cmake for the psmoveapi
mkdir build
cd build
cmake .. -G "MinGW Makefiles"
Alternatively, if you want to use the CL Eye SDK:
cmake .. -G "MinGW Makefiles" -DPSMOVE_USE_CL_EYE_SDK=ON
8. finally build
mingw32-make (XXX: Is this still correct for mingw-w64?)
9. start one of the desired test applications