frodovdr/pvr.octonet
1
0
Fork 0
mirror of https://github.com/DigitalDevices/pvr.octonet.git synced 2023-10-10 13:36:57 +02:00
Code Issues Releases Wiki Activity
42 Commits 7 Branches 34 Tags 227 KiB
C++ 95.8%
Gettext Catalog 2.5%
CMake 1.7%
e9f0d6bf76
Go to file
Alwin Esch e9f0d6bf76 Remove not used part
2017-05-03 09:47:39 +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 Bump version to 0.3.6 2016-11-28 15:09:54 +01:00
src Remove not used part 2017-05-03 09:47:39 +02:00
.gitignore Ignore build directory 2016-10-05 10:40:23 +02:00
.travis.yml Add travis build instructions 2016-11-04 11:26:48 +01:00
appveyor.yml Add appveyor build instructions 2016-11-04 11:50:22 +01:00
CMakeLists.txt Build fixes for Windows 2016-10-05 16:46:40 +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

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.