Kodi Krypton

[donald]

Hi
It was late at night...so all the following is IIRC..

You need the libcdio-0.93-i486-1.xzm module
It should be available via USM

LOGIN AS ROOT

Copy the Kodi 17.1 module into /tmp and extract it.
(shorten the name of the resulting folder to kodi)

Extract the libcdio-0.93-i486-1.xzm module.
In ../usr/lib/ are two files (among others)
libcdio.so.16 (which is a link) and a shared library libcdio.so.16.0.0

Copy the two files into /tmp/kodi/usr/lib/

Now rebuild the module.
Open a terminal and run:
dir2xzm /tmp/kodi /tmp/kodi-17.1-whatever.xzm

If all goes well, the final module will be in /tmp
(and should work with porteus 4.0 32bit xfce).

[rchase]

Thanks -- the module appears to run. I have posted a link to it in the i486 modules section.

[Rava]

Code: Select all

root@porteus:/tmp/bla# dir2xzm /tmp/your-app-name-folder /tmp/app-name-bundle.xzm

-- the bundle is ready and you can now delete the temporary used folders --
( /tmp/bla and /tmp/whatever-the-app-name-was )

Of course the bundle itself lies on the temp folder, which is, most probably, only in your RAM disk. (And stuff in /tmp usually never gets saved in the save dat file of Porteus.) So of course you need to copy it somewhere safe, e.g. your porteus/optional folder or any other place you store Porteus modules that should not be automatically activated during startup.

To most users the above should be obvious that creating the module like donald explained and then reboot would result in no module anywhere whatsoever. I just want to point out the obvious for the ones who not see it as that obvious.

[donald]

Yep, you're absolutely right....thanks..
I seemingly assume too often, "Everyone knows that".

[Rava]

Yep, you're absolutely right....thanks..
I seemingly assume too often, "Everyone knows that".

Still, you are not responsible for the user's actions. They should get to know the system they are running, it is up to them.
And the /tmp or /temp folder being on a RAM disc, if you ask me that is a clever way in any case. Why would e.g. SM-Witless OS have these permanently stored on the users hard disk?

[Rava]

Trying to run donald's kodi module using XFCE version of Porteus 5.0rc1:

Code: Select all

guest@porteus:/$ ldd /usr/lib64/kodi/kodi.bin|grep not
	libcdio.so.16 => not found
	libva.so.1 => not found
	libva-drm.so.1 => not found
	libva-x11.so.1 => not found
	libhogweed.so.4 => not found
	libnettle.so.6 => not found
	libidn.so.11 => not found

Seems some dependencies are not met for now.

Hopefully when I manually fix all these, no new ones pop up. I kind of dislike dependency hell.

Update
What is worse, as long as I had the Kodi module activated, other python scripts (e.g. youtube-dl) have been broken, so it seems the old Kodi module is not compatible with Porteus 5.0rc1.

Donald, would you be able to create a new version for 5.0rc1 that would run in XFCE or Openbox? That would be very much appreciated.