Login at Kodi Home

topfs2 · 2015-02-27, 09:39

(2015-02-26, 09:25)Odon Wrote: I had to replace boost:: by std:: in xbmc/interfaces/json-rpc/FileOperations.cpp when mergin your branch in latest master. Is it expected ?

I've been a bit busy IRL sadly, but I'll try to rebase the headless branch ASAP on my new appparser one.

bibi · 2015-02-27, 09:50

Hi,

One thing i dont get with this version is if you all set up kodi with guisetting.xml or if you use another way ?

In the case you use guisetting, a copy and past from my main computer with its library could be enough to initialise the kodi server ?

Bibi

topfs2 · 2015-02-27, 10:00

(2015-02-27, 09:50)bibi Wrote: Hi,

One thing i dont get with this version is if you all set up kodi with guisetting.xml or if you use another way ?

In the case you use guisetting, a copy and past from my main computer with its library could be enough to initialise the kodi server ?

Bibi

There is APIs to set it up via JSON RPC, however there is no webinterface which provides it so far. So yeah, for now the easiest is probably to do it via gui (you can start the compiled with gui and then start it without).
In general we start some services needed so most should be ready from the start, but sources etc aren't which needs to be configured.

Consider this version a prerelease, we together here are working on making it simple. So in the long run when you start headless you'll be able to go to a website and set it up simply.

StealthDefender · 2015-02-27, 10:11

Is there a way to let headless kodi safe the stats direct to the nfo and save scraped pictures in the movie folder?
Greetz Stealth

bibi · 2015-02-27, 22:40

Thanks Topfs2 for the explanation !
Will see this weekend if i can launch it through an ssh x session.

Bibi

lordvader · (This post was last modified: 2015-02-28, 09:08 by lordvader.)

Hey all.
I've just compiled headless kodi, but I get a coredum on start.
I've uploaded the crash log here : http://pastebin.com/E4WVpnBa

Also, this is the output on the command line :

Code:
libGL error: failed to lead driver: swrast

I'm running this on an intel i5 nuc, if that helps ...

Let me know if you need more info.

... wait ... I may have built the wrong branch ... I'll keep you posted

Yeah - forgot to switch to the helix_headless branch. Building now Smile

XBL. · (This post was last modified: 2015-03-01, 14:20 by XBL..)

Hey guys,

I just started on getting this to work. My current headless install is still a Gotham version, build with the old instructions (from the minified thread). I'm now trying to build Helix according to the steps in this post. However, it seems to fail on taglib.

The thing is, I already have the taglib 1.8 lib on my server (was also necessary for Gotham). I even tried to install it again, but that didn't make a difference. I've also added '--enable-shared-lib' to the config options (used it on the Gotham build), but that didn't help.

The errors I get: http://pastebin.com/fUQTLLGh

I'm kinda lost now, so hopefully any of you guys have an idea of what's going wrong.

Btw, OS is Ubuntu 12.04.

**Martijn** · 2015-03-01, 14:05

use pastebin.com for logs

XBL. · 2015-03-01, 14:20

(2015-03-01, 14:05)Martijn Wrote: use pastebin.com for logs

My bad. Fixed it.

sparklyballs · 2015-03-01, 17:03

(2015-03-01, 14:04)XBL. Wrote: Hey guys,

I just started on getting this to work. My current headless install is still a Gotham version, build with the old instructions (from the minified thread). I'm now trying to build Helix according to the steps in this post. However, it seems to fail on taglib.

The thing is, I already have the taglib 1.8 lib on my server (was also necessary for Gotham). I even tried to install it again, but that didn't make a difference. I've also added '--enable-shared-lib' to the config options (used it on the Gotham build), but that didn't help.

The errors I get: http://pastebin.com/fUQTLLGh

I'm kinda lost now, so hopefully any of you guys have an idea of what's going wrong.

Btw, OS is Ubuntu 12.04.

I built it in a docker using 12.04 when i was trying different builds etc... i triggered a re build on docker hub earlier and it built ok, just pulling the docker now to run test it.

XBL. · 2015-03-01, 17:13

(2015-03-01, 17:03)sparklyballs Wrote: I built it in a docker using 12.04 when i was trying different builds etc... i triggered a re build on docker hub earlier and it built ok, just pulling the docker now to run test it.

Just to clarify: I didn't use the docker, I merely used those command instructions (although that should mean the same thing).

sparklyballs · 2015-03-01, 17:16

(2015-03-01, 17:13)XBL. Wrote:
(2015-03-01, 17:03)sparklyballs Wrote: I built it in a docker using 12.04 when i was trying different builds etc... i triggered a re build on docker hub earlier and it built ok, just pulling the docker now to run test it.

Just to clarify: I didn't use the docker, I merely used those command instructions (although that should mean the same thing).

uh huh, that was for wheezy though, this one is specifically for 12.04.

if you're comfortable with translating the docker across to standard linux here is the git repo for it, use the taglib that's in the repo. (in src folder)

https://github.com/sparklyballs/12.04-kodi-headless

XBL. · 2015-03-01, 17:23

(2015-03-01, 17:16)sparklyballs Wrote: uh huh, that was for wheezy though, this one is specifically for 12.04.

if you're comfortable with translating the docker across to standard linux here is the git repo for it, use the taglib that's in the repo. (in src folder)

https://github.com/sparklyballs/12.04-kodi-headless

Thanks! I'm gonna give that a go. I'll report back when I know more.

XBL. · (This post was last modified: 2015-03-02, 13:31 by XBL..)

Ok, I found the problem. It was libtag1-dev still being on my system. Since the makefile first looks in /usr/lib/x86_64-linux-gnu/ and then /usr/local/lib, it will use the wrong one. Interestingly, the docker file does contain instructions to (re)install libtag1-dev after finishing the build, but no instructions to remove it first.

Now on to the next thing: how to actually compile Helix instead of 15.0-alpha (which I have now) and get it to work. For now it exits with "ERROR: Unable to create GUI. Exiting". It doesn't even seem to do anything with the --headless switch. It's also not listed when doing kodi --help, although I don't know if it's supposed to be.

EDIT: nvm. Yesterday I pulled the source again after moving some stuff around which broke a few paths, but forgot to checkout the headless branch. Don't code and drink, kids!

sparklyballs · 2015-03-02, 13:12

(2015-03-02, 13:09)XBL. Wrote: Ok, I found the problem. It was libtag1-dev still being on my system. Since the makefile first looks in /usr/lib/x86_64-linux-gnu/ and then /usr/local/lib, it will use the wrong one. Interestingly, the docker file does contain instructions to (re)install libtag1-dev after finishing the build, but no instructions to remove it first.

Now on to the next thing: how to actually compile Helix instead of 15.0-alpha (which I have now) and get it to work. For now it exits with "ERROR: Unable to create GUI. Exiting". It doesn't even seem to do anything with the --headless switch. It's also not listed when doing kodi --help, although I don't know if it's supposed to be.

it's a docker and there's no need to uninstall libtag first because it was never there to start with