Building out-of-tree (recommended)

Linux

Create and enter a build directory

mkdir peripheral.joystick
cd peripheral.joystick

Generate a build environment with config for debugging

cmake -DADDONS_TO_BUILD=peripheral.joystick \
      -DCMAKE_BUILD_TYPE=Debug \
      -DCMAKE_INSTALL_PREFIX=$HOME/workspace/xbmc/addons \
      -DPACKAGE_ZIP=1 \
      $HOME/workspace/xbmc/project/cmake/addons

The add-on can then be built with make.

Building stand-alone (development)

Stand-alone builds are closer to "normal" software builds. The build system looks for its dependencies, by default with /usr and /usr/local prefixes.

To provide these dependencies yourself in a local working directory ($HOME/kodi), build Kodi with an installation prefix

./configure --prefix=$HOME/kodi
make
make install

Clone kodi-platform and create a CMake build directory

git clone https://github.com/xbmc/kodi-platform.git
cd kodi-platform
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Debug \
      -DCMAKE_INSTALL_PREFIX=$HOME/kodi \
      ..
make
make install

With these dependencies in place, the add-on can be built. Point CMake to the add-on's build system instead of $HOME/workspace/xbmc/project/cmake/addons

cmake -DCMAKE_BUILD_TYPE=Debug \
      -DCMAKE_INSTALL_PREFIX=$HOME/workspace/xbmc/addons \
      -DCMAKE_PREFIX_PATH=$HOME/kodi \
      -DPACKAGE_ZIP=1 \
      ..

Building in-tree (cross-compiling)

Kodi's build system will fetch the add-on from the GitHub URL and git hash specified in peripheral.joystick.txt.

Linux

Ensure that kodi has been built successfully. Then, from the root of the source tree, run

make install DESTDIR=$HOME/kodi

Build the add-on

make -C tools/depends/target/binary-addons PREFIX=$HOME/kodi ADDONS="peripheral.joystick"

The compiled .so can be found at

$HOME/kodi/lib/kodi/addons/peripheral.joystick/peripheral.joystick.so

To rebuild the add-on or compile a different one, clean the build directory

make -C tools/depends/target/binary-addons clean

Windows

We will use CMake to generate a kodi-addons.sln Visual Studio solution and project files. Add-ons can be built individually through their specific project, or all at once by building the solution.

First, download and install CMake.

Run the script from PR 6658 to create Visual Studio project files

tools\windows\prepare-binary-addons-dev.bat

The generated solution can be found at

project\cmake\addons\build\kodi-addons.sln

No source code is downloaded at the CMake stage; when the project is built, the add-on's source will be downloaded and compiled.

OSX

Per README.osx, enter the tools/depends directory and make the add-on:

cd tools/depends
make -C target/binary-addons ADDONS="peripheral.joystick"

To rebuild the add-on or compile a different one, clean the build directory

make -C target/binary-addons clean