Skip to content

Latest commit

 

History

History
121 lines (88 loc) · 4.58 KB

BUILD.md

File metadata and controls

121 lines (88 loc) · 4.58 KB

Building HIDAPI from Source

Table of content

Intro

For various reasons you may need to build HIDAPI on your own.

It can be done in several different ways:

Autotools build system is historically first mature build system for HIDAPI. Most common usage of it is in its separate README: BUILD.autotools.md.
NOTE: for all intentions and purposes the Autotools build scripts for HIDAPI are deprecated and going to be obsolete in the future. HIDAPI Team recommends using CMake build for HIDAPI.

CMake build system is de facto an industry standard for many open-source and proprietary projects and solutions. HIDAPI is one of the projects which uses the power of CMake for its advantage. More documentation is available in its separate README: BUILD.cmake.md.

If you don't know where to start to build HIDAPI, we recommend starting with CMake build.

Prerequisites:

Regardless of what build system system you choose to use, there are specific dependencies for each platform/backend.

Linux:

Depending on which backend you're going to build, you'll need to install additional development packages. For linux/hidraw backend you need development package for libudev. For libusb backend, naturally, you need libusb development package.

On Debian/Ubuntu systems these can be installed by running:

# required only by hidraw backend
sudo apt install libudev-dev
# required only by libusb backend
sudo apt install libusb-1.0-0-dev

FreeBSD:

On FreeBSD you will need to install libiconv. This is done by running the following:

pkg_add -r libiconv

Mac:

On Mac make sure you have XCode installed and its Command Line Tools.

Windows:

On Windows you just need a compiler. You may use Visual Studio or Cygwin/MinGW, depending on which environment is best for your needs.

Embedding HIDAPI directly into your source tree

Instead of using one of the provided standalone build systems, you may want to integrate HIDAPI directly into your source tree.


If your project uses CMake as a build system, it is safe to add HIDAPI as a subdirectory.


If the only option that works for you is adding HIDAPI sources directly to your project's build system, then you need:

  • include a single source file into your project's build system, depending on your platform and the backend you want to use:
  • add a hidapi folder to the include path when building hid.c;
  • make the platform/backend specific dependencies available during the compilation/linking, when building hid.c;

NOTE: the above doesn't guarantee that having a copy of <backend>/hid.c and hidapi/hidapi.h is enough to build HIDAPI. The only guarantee that <backend>/hid.c includes all nesessary sources to compile it as a single file.

Check the manual makefiles for a simple example/reference of what are the dependencies of each specific backend.

Building the manual way on Unix platforms

Manual Makefiles are provided mostly to give the user an idea what it takes to build a program which embeds HIDAPI directly inside of it. These should really be used as examples only. If you want to build a system-wide shared library, use one of the build systems mentioned above.

To build HIDAPI using the manual Makefiles, change to the directory of your platform and run make. For example, on Linux run:

cd linux/
make -f Makefile-manual

Building on Windows

To build the HIDAPI DLL on Windows using Visual Studio, build the .sln file in the windows/ directory.

To build HIDAPI using MinGW or Cygwin using Autotools, use a general Autotools instruction.

Any windows builds (MSVC or MinGW/Cygwin) are also supported by CMake.

If you are looking for information regarding DDK build of HIDAPI:

  • the build has been broken for a while and now the support files are obsolete.