Go to file
Alwin Esch cd774b6edc change to automatic depends set on addon.xml 2017-05-18 12:04:46 +02:00
debian Unify Digital Devices naming 2016-11-11 20:49:27 +01:00
depends/common/jsoncpp depdends: Import JsonCpp 2016-02-02 11:03:40 +01:00
pvr.octonet change to automatic depends set on addon.xml 2017-05-18 12:04:46 +02:00
src libXBMC_codec.h removed and changed to libXBMC_pvr.h also fix compile fault after last request 2017-05-03 09:48:00 +02:00
.gitignore change to automatic depends set on addon.xml 2017-05-18 12:04:46 +02:00
.travis.yml Add travis build instructions 2016-11-04 11:26:48 +01:00
CMakeLists.txt change to automatic depends set on addon.xml 2017-05-18 12:04:46 +02:00
FindJsonCpp.cmake depdends: Import JsonCpp 2016-02-02 11:03:40 +01:00
README.md README: Rewrite build instructions 2016-11-28 14:00:01 +01:00
appveyor.yml Add appveyor build instructions 2016-11-04 11:50:22 +01:00

README.md

Octonet PVR

Digital Devices Octonet PVR client addon for Kodi

Platform Status
Linux + OS X (Travis) Build Status
Windows (AppVeyor) Build status

Building

These instructions work on all supported platforms for the most part. Obviously, paths need to be adjusted according to your OS (/ vs \). We use Linux paths here as an example.

Clone the pvr.octonet repository:

$ git clone https://github.com/DigitalDevices/pvr.octonet.git

Clone the Kodi repository:

$ git clone https://github.com/xbmc/xbmc.git

If you already have a local Kodi checkout, you can use that one. Just make sure it is recent enough (Kodi 17 Beta 5 or later should work).

$ cd pvr.octonet
$ mkdir build
$ cd build
$ cmake -DCMAKE_BUILD_TYPE=Release -DADDONS_TO_BUILD="pvr.octonet" -DADDON_SRC_PREFIX="path to parent of pvr.octonet" -DCMAKE_INSTALL_PREFIX="install" -DPACKAGE_ZIP=ON "path to kodi/project/cmake/addons"

On Windows, you should add -G "NMake Makefiles" to the CMake invocation. Make sure that ADDON_SRC_PREFIX does not point directly to pvr.octonet but instead to its parent directory.

Finally, build the plugin with make (or nmake on Windows). The plugin should be in an install subdirectory.