> Looking closer at kodi it turns out it has a -l /--lircdev CLI option.
> problem solved. This also means that thomas can walk-around the problem
> by configuring kodi instead of using the symlink.
Yes and that is the way I do it right now. This is for me the save way
to solve future changes.
On 07/01/17 03:55, Alec Leamas wrote:
Just syncing is of course the first, minimal step. But bottom line is
that a lirc user could set the (typically secondary) device to anything,
it's just a config file. So a compile-time setting will not make in the
long run. Other apps e. g., mythTV has it
On 07/01/17 02:57, Bálint Réczey wrote:
Hi,
A proper fix for this needs to be something accepted by upstream, I guess.
Kodi's build system allows setting the default device through a
./configure option
thus I think this does not have to be upstreamed.
Do you mean upstreaming a more comp
Hi,
2017-01-06 21:27 GMT+01:00 Alec Leamas :
> On Fri, 06 Jan 2017 20:27:05 +0100 Thomas Renard wrote:
>
>>
>> kodi is hard coded to the wrong "device" path to lirc.
>> The binary tries /dev/lircd but the "device" (which is a socket!)
>> can be found at /var/run/lirc/lircd.
>
> Hi!
>
> lirc maint
On Fri, 06 Jan 2017 20:27:05 +0100 Thomas Renard wrote:
>
> kodi is hard coded to the wrong "device" path to lirc.
> The binary tries /dev/lircd but the "device" (which is a socket!)
> can be found at /var/run/lirc/lircd.
Hi!
lirc maintainer speaking... note that the /var/run/lirc/lircd path j
Package: kodi
Version: 2:17.0~beta6+dfsg1-1
Severity: normal
Dear Maintainer,
kodi is hard coded to the wrong "device" path to lirc.
The binary tries /dev/lircd but the "device" (which is a socket!)
can be found at /var/run/lirc/lircd.
- write ~/.kodi/userdata/Lircmap.xml according to working i
