<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
<meta http-equiv="X-UA-Compatible" content="IE=9"/>
<meta name="generator" content="Doxygen 1.8.11"/>
<title>xwiimote: Overview</title>
<link href="tabs.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="jquery.js"></script>
<script type="text/javascript" src="dynsections.js"></script>
<link href="navtree.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="resize.js"></script>
<script type="text/javascript" src="navtreedata.js"></script>
<script type="text/javascript" src="navtree.js"></script>
<script type="text/javascript">
$(document).ready(initResizable);
$(window).load(resizeHeight);
</script>
<link href="doxygen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div id="top"><!-- do not remove this div, it is closed by doxygen! -->
<div id="titlearea">
<table cellspacing="0" cellpadding="0">
<tbody>
<tr style="height: 56px;">
<td id="projectalign" style="padding-left: 0.5em;">
<div id="projectname">xwiimote
 <span id="projectnumber">2</span>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<!-- end header part -->
<!-- Generated by Doxygen 1.8.11 -->
<div id="navrow1" class="tabs">
<ul class="tablist">
<li class="current"><a href="index.html"><span>Main Page</span></a></li>
<li><a href="modules.html"><span>Modules</span></a></li>
<li><a href="annotated.html"><span>Data Structures</span></a></li>
<li><a href="files.html"><span>Files</span></a></li>
</ul>
</div>
</div><!-- top -->
<div id="side-nav" class="ui-resizable side-nav-resizable">
<div id="nav-tree">
<div id="nav-tree-contents">
<div id="nav-sync" class="sync"></div>
</div>
</div>
<div id="splitbar" style="-moz-user-select:none;"
class="ui-resizable-handle">
</div>
</div>
<script type="text/javascript">
$(document).ready(function(){initNavTree('index.html','');});
</script>
<div id="doc-content">
<div class="header">
<div class="headertitle">
<div class="title">Overview </div> </div>
</div><!--header-->
<div class="contents">
<div class="textblock"><p>xwiimote is an open-source device driver for Nintendo Wii / Wii U remotes. It contains tools and libraries which work together with the official hid-wiimote kernel driver, available since linux-3.1.</p>
<p>If you want to use a Nintendo Wii Remote or any compatible device (including the Nintendo Wii Balance Board, Nintendo Wii U Pro Controller, and more) on your linux system, the xwiimote software stack provides everything you need.</p>
<p>This distribution is hosted at: <a href="http://dvdhrm.github.io/xwiimote">http://dvdhrm.github.io/xwiimote</a> Use this website to contact the maintainers or developers or to file bug reports.</p>
<h1>Install </h1>
<p>To install the libxwiimote.so library and the related tools, use: $ ./configure [–enable-debug] [–prefix=/usr] $ make $ make install If "configure" is not available, use: $ ./autogen.sh [<configure-flags>]</p>
<p>Dependencies:</p><ul>
<li>libudev: Used for device enumeration</li>
<li>ncurses: Used for UI of xwiishow</li>
</ul>
<p>This software packages contains: libxwiimote.so: A userspace library which helps accessing connected Wii Remotes in the system. It can be used by applications to use Wii Remotes as input. You can also use the direct kernel interface, though. xwiishow: A test application which lists all connected Wii Remotes. If a Wii Remote is passed as argument, it continuously reads input from the device and prints it to the screen. 50-xorg-fix-xwiimote.conf: X configuration file which should be installed into /etc/X11/xorg.conf.d/ by your distribution. It adds all Wii Remotes to the input blacklist of the X-server. This is needed since the raw Wii Remote kernel interface is useless (even irritating) to the X-server. Instead the xf86-input-xwiimote driver should be used. manpages: Several manpages are provided. One overview page and several other pages for each tool and feature. They are installed by the autotools scripts automatically alongside the library and applications.</p>
<p>The following tools are available but not installed into the system: xwiidump: A test application which reads the EEPROM memory of a connected Wii Remote and prints it to stdout. This requires debugfs support in the kernel and the hid-wiimote kernel module.</p>
<p>Following software is not part of this package: hid-wiimote.ko: The wiimote kernel module is available in the official linux kernel sources and should already be installed in your system if you run linux-3.1 or newer. wiimote.so: The BlueZ bluetoothd wiimote plugin is part of the upstream BlueZ package and available since bluez-4.96. It should be already installed on your system.</p>
<h1>Usage </h1>
<p>Please see the website for help: <a href="http://dvdhrm.github.io/xwiimote">http://dvdhrm.github.io/xwiimote</a></p>
<h1>Documentation </h1>
<p>./doc/website/index.html: Official website of XWiimote and documentation ./doc/*.3: Manpages ./doc/DEVICES: Enumeration of all Nintendo Wii / Wii U related devices ./doc/DEV_*: Device communication/protocol descriptions</p>
<h1>Development </h1>
<p>Please see ./DEV for development information.</p>
<h1>Copying </h1>
<p>Please see ./COPYING for more information.</p>
<h1>Compatibility </h1>
<p>Two other commonly used Wii-Remote libraries are cwiid and wiiuse. Both provide a full user-space driver and were used heavily in the past. We do not provide API compatibility to them as both APIs are very restricted: </p><pre class="fragment">- cwiid: This API is highly asynchronous with threads. It does not allow
a single-threaded application to use it. This makes it very hard to
use and we decided not to provide a compatibility layer as we do not
want to support such library-API designs.
- wiiuse: This API is tightly bound to the idea that the application is
supposed to discover and connect the Bluetooth devices. It uses a
static array for all used Wii Remotes and requires callbacks for
notification. Same as cwiid, we do not provide a compatibility layer
as the API is very different from our API.
</pre><p>We designed our API to have as few restrictions as possible. We do not force an application to use a special programming technique. Instead, an application can use our API to support event-based, callback-based or thread-based event-loops or any other kind that it wants. We achieve this by keeping the user-space API very similar to the kernel-API so the application can integrate this into any infrastructure it wants.</p>
<h1>Contact </h1>
<p>Website: <a href="http://dvdhrm.github.io/xwiimote">http://dvdhrm.github.io/xwiimote</a></p>
<p>For email contact please see ./COPYING for a list of contributors or write an email to the current maintainer at: <a href="#" onclick="location.href='mai'+'lto:'+'dh.'+'he'+'rrm'+'an'+'n@g'+'ma'+'il.'+'co'+'m'; return false;">dh.he<span style="display: none;">.nosp@m.</span>rrma<span style="display: none;">.nosp@m.</span>nn@gm<span style="display: none;">.nosp@m.</span>ail.<span style="display: none;">.nosp@m.</span>com</a> </p>
</div></div><!-- contents -->
</div><!-- doc-content -->
<!-- start footer part -->
<div id="nav-path" class="navpath"><!-- id is needed for treeview function! -->
<ul>
<li class="footer">Generated on Mon Jan 4 2016 12:47:27 for xwiimote by
<a href="http://www.doxygen.org/index.html">
<img class="footer" src="doxygen.png" alt="doxygen"/></a> 1.8.11 </li>
</ul>
</div>
</body>
</html>
distrib
>
Mageia
>
6
>
i586
>
media
>
core-release
>
by-pkgid
>
c6096529d306783d0895db365bd224ce
>
files
>
38
