Kodi Krypton

Technical issues/questions of an intermediate or advanced nature.
donald
Full of knowledge
Full of knowledge
Posts: 1481
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

Kodi Krypton

Post#31 by donald » 12 Oct 2018, 18:00

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
Samurai
Samurai
Posts: 185
Joined: 10 Jan 2016, 17:26
Distribution: Porteus 4.0 xfce x64
Location: Denver, Colorado

Kodi Krypton

Post#32 by rchase » 13 Oct 2018, 21:48

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

User avatar
Rava
Contributor
Contributor
Posts: 2038
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 4.0 x86-64 XFCe
Location: Forests of Germany

Re: Kodi Krypton

Post#33 by Rava » 09 Jan 2019, 05:40

donald wrote:
20 Jun 2017, 08:45

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. :D
Cheers!
Yours Rava

donald
Full of knowledge
Full of knowledge
Posts: 1481
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

Re: Kodi Krypton

Post#34 by donald » 09 Jan 2019, 10:49

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

User avatar
Rava
Contributor
Contributor
Posts: 2038
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 4.0 x86-64 XFCe
Location: Forests of Germany

Re: Kodi Krypton

Post#35 by Rava » 09 Jan 2019, 12:36

donald wrote:
09 Jan 2019, 10:49
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?
Cheers!
Yours Rava

Post Reply