Open mdeguzis opened 7 years ago
You should use cmake to configure and make/ninja to build OpenPHT. The autotools files is a leftover from the old Kodi/Xbmc code base and have/should never been used for PHT/OpenPHT.
OpenPHT-Embedded is just a fork of LibreELEC that builds and include OpenPHT instead of Kodi, but I suggest you look at the package.mk
file for the plexht
package for some inspiration.
This is how OpenPHT is configured and coss-compiled on the Embedded builds: https://github.com/RasPlex/OpenPHT-Embedded/blob/openpht-1.7/packages/mediacenter/plexht/package.mk#L223-L244
After looking at https://github.com/ValveSoftware/steamlink-sdk/blob/master/examples/kodi/kodi.patch I think it should be possible to adjust this patch to make it apply on top of OpenPHT. Most playback/rendering/audio/video parts of OpenPHT is close to Kodi Jarvis so most parts related to video/audio should be rather trivial to port, however the settings system is more close to Frodo so any code that uses the settings api will need some work.
Finally you need to add support for the Steam Link in the cmake files, suggest you look the changes to cmake files in https://github.com/RasPlex/OpenPHT/commit/26c310f95d5b5c4e288f2c4380be1fc0dd9dec4d (added amlogic support).
I'll start looking at all this information. Thank you for a start at least giving this is the "College Try" :)
I noticed that cmake/python is not included in the Steam Link SDK. Like the Kodi readme, I believe I can just install my binary on Debian Jessie and continue on with some other pieces to fix. If I actually get this working eventually, I'll submit a PR.
I add a task list to the top in case anyone wants to help out.
Updated uname/CPU details for the curious. Obtained via SSH. Keep in mind, even if this works out, you will need to source the Steam Link SDK to build. It is required.
Thanks @ProfessorKaos64 for getting on this! I'm not much of a linux / terminal whiz but can do some basic things if needed? Would be great to have this running on Link.
@pjpalomaki , just follow my commits on my fork, the fork of Steam Link SDK I have (branch "openpht") and this thread / task list. Anything I have not already added/reported/tested, just see where you can get. Round up support, or pull in a friend who can help. I'd like to keep the commits central to my fork of this repo (branch "steamlink-openpht-1.7") if possible. People seem to ask for this frequently, and it should* be possible. I'm no traditional programmer, but resourceful with Linux.
@ProfessorKaos64 it appears your fork of the steamlink sdk is 10 commits behind Valve's master
branch. Is there a reason you forked at the commit you did?
Done, master/openpht updated. It was mainly Kodi fixes.
I am having a bit of trouble with the libs if anyone wants to test the current build_steamlink.sh
script. Want to make sure I am not digging myself a hole. Also bear in mind, Plex Media Player is now available for Kodi.
I am going to try my hand at building this on Steam Link (ARMv7) for fun, and some have asked for it. I saw there was OpenPHT-Embedded as well. Kodi is most certainly doable, so there should be a way as well to build OpenPHT.
Would running this (in general), or utilizing that project be more beneficial? Please see the kodi script as a comparison. Kodi has
tools/depends/Makefile
in which you run./configure
to build the deps.My aim is to try and port OpenPHT, but I want to make sure I am looking in the right place, here or openpht-embedded? I don't mind digging into the project at all, just a bit of guidance. I know this is possible.
If I try to bootstrap this on an embedded system, I get: http://sprunge.us/VOZc
Build script: steamlink-sdk
Porting Progress
URL: https://github.com/ProfessorKaos64/OpenPHT/tree/steamlink-openpht-1.7