2014-12-23, 13:50
(2014-12-23, 13:39)topfs2 Wrote:(2014-12-23, 10:47)xexe Wrote: What is the purpose of server.xml?
It contains override settings which are in effect when you run in headless mode, so it probably should be named headless.xml
(2014-12-23, 01:46)sparklyballs Wrote:(2014-12-23, 01:42)topfs2 Wrote: I've recently been trying to gather up some patches and fix those things that depend on the gui in kodi so that we may at one point have a headless version of Kodi.
In general my goal is to split out my efforts over multiple PRs so that master gets better and better.
But for those interested I have pulled in all needed patches for my initial headless version of kodi on a base of Helix. Which can be found over at my repository https://github.com/topfs2/xbmc/tree/helix_headless
The initial attempt here is not to compile down a stripped version of kodi just for headless use, but rather to disable the gui on start. This means that it can replace a Helix and if its headless or not is only choosen via the startup argument --headless.
When headless uPnP and Webserver are default to on, as what point is headless if you can't connect to it
To run after compile simply
Please let me know of any bugs and crashes when running in headless so we can get headless into master ASAP!
Cheers,
Tobias
Could this be dockerised as there is a lot of interest on this over on the unraid forum as they have a docker base in the beta of uraid 6 and unraid and xbmc have been happy bedfellows for a long time.
ignore my silly question, lol.
it's a branch of source, got confused and thought it was something else.
just about to run a build.
ignore my silly question, lol.
it's a branch of source, got confused and thought it was something else.
just about to run a build.
my configure options,
./configure \
--enable-nfs \
--enable-upnp \
--enable-ssh \
--enable-libbluray \
--disable-debug \
--disable-vdpau \
--disable-vaapi \
--disable-crystalhd \
--disable-vdadecoder \
--disable-vtbdecoder \
--disable-openmax \
--disable-joystick \
--disable-rsxs \
--disable-projectm \
--disable-rtmp \
--disable-airplay \
--disable-airtunes \
--disable-dvdcss \
--disable-optical-drive \
--disable-libusb \
--disable-libcec \
--disable-libmp3lame \
--disable-libcap \
--disable-udev \
--disable-libvorbisenc \
--disable-asap-codec \
--disable-afpclient \
--disable-goom \
--disable-fishbmc \
--disable-spectrum \
--disable-waveform \
--disable-avahi \
--disable-non-free \
--disable-texturepacker \
--disable-pulse \
--disable-dbus \
--disable-alsa \
--disable-hal && \
do these look good to you ? anything else to disable, my personal choice is for bluray enabled as i have a lot of bluray rips.
The intent of my branch is to run without any disables, i.e. a fully functional kodi but with the GUI disabled. So its fully possible to play music on it etc.
This is because we/I am aiming towards platforms were GUI is available but you might not want to run it. For example if you have kodi installed on your windows box it could potentially always boot up in headless mode, starting kodi via menu would simply trigger the GUI creation and "exit" would mean that it simply closes the GUI while headless remains. Much like how steams big picture behaves.
However, in a NAS environment it will always be beneficial to disable, as there is never a GUI available, and packages with gui makes no sense. But thats not my personal main goal, as that should be very possible to do no matter.
I ran my build last night and had a little explore with it earlier, not certain if it is a vagary of docker but i had to start it, let it run for a few minutes and then stop/start it again before i could get the web interface and ping it from sickbeard etc...
That aside though, it seems stable when browsing music in the web app which in headless trips it up sometimes.
