Re: Fwd: Re: Lircd Socket - Irexec will not connect

[Alec L. <lea...@gm...>]

On 13/04/15 21:25, James A R Brown wrote:

>
> On 13/04/15 13:38, Alec Leamas wrote:
>> On 13/04/15 12:09, James A R Brown wrote:
>>> Hummm.... /usr/local/var/run/lirc/lircd is default created path for my
>>> configure?
>>
>> These are the autotools defaults. The
>re are many ways to change this,
>> one is to use --prefix=... to configure, another to use the runtime
>> --output option  on command line or in lirc_options.conf
>>
>> Packaged versions normally sets prefix to /usr -> default socket
>> becomes /var/run/lirc/lircd
>>
>>
>> Cheers!
>>
>> --alec
>>
>> PS: Please don't top-post. DS
>>
>
 > Hi Alec,
 >
 > To clarify your mail
 >
 > If i set the prefix to /usr the socket then created is at
 > /usr/var/run/lirc/lircd not /var/run/lirc/lircd as your mail says.
 >
 > So I guess the prefix should be "" to get /var/run/lirc/lircd socket
 > which is the default place irw, irsend etc look too?

No

 > So that said, should a default build with no configure options, not put
 > the lircd socket exactly where the lirc apps expect?
 >
 > And only not do that, when a --prefix= option on the configure is used?

This is basically not directly related to lirc, it's more about how 
autotools works. You might want to have a second look at the configure 
--help output and/or look into the autoconf/automake documentation.

That said, it's generally a little tricky to have a non-standard 
installation. If you just want to test, CONTRIBUTE.md in the source top 
directory has info on how to run lircd and other tools directly from the 
build directory without installing.

Cheers!

--alec

PS: Again: Please don't top-post. DS