[mythtv-users] lirc and Xine

[Buechler, Mark R]

strace xine.. look for the system call which tries to open the device.

-----Original Message-----
From: malcolm [mailto:mythtv at lds.dyndns.org]
Sent: Saturday, April 03, 2004 12:17 PM
To: Discussion about mythtv
Subject: Re: [mythtv-users] lirc and Xine


----- Original Message -----
From: "Steven Cruysberghs" <steven.cruysberghs at pi.be>
Sent: Saturday, April 03, 2004 5:29 AM


> if i remember corectly (unf. my source folder has been deleted) running
> configure detected lirc on my system (Slackware) and automaticly included
> it.
>
> If it doesn't try running configure --help | grep lirc

I did run "./configure --help |grep lirc" (see towards bottom of thread).
All I get is "--disable-lirc".  There is no specific enable option.  Just
for the hell of it though I recompiled xine with --enable-lirc just to see
what it would do.

Here's a new though.  Could xine be looking for /dev/lirc ?  Since my lirc
dev is actually /dev/lirc/lirc0 I couldn't even make a symlink to it since
/dev/lirc is a directory already there.
Is there a way I can verify which /dev/ device xine is looking for?  and
perhaps change it if need be?

Thanks
Malcolm


> > ----- Original Message -----
> > From: "Steven Cruysberghs" <steven.cruysberghs at pi.be>
> > Sent: Friday, April 02, 2004 8:47 AM
> >
> >
> >> this is my ~/.lircrc file for mplayer (with I use for mythvideo) and
> >> xine
> >> (mythdvd)
> >>
> >> I recomplied xine-lib and xine-ui myself to get lirc working.
> >
> > When you recompiled xine-lib and xine-ui did you have to give it any
> > special
> > parameters or options to get it working?  I've recompiled my xine-lib
and
> > xine-ui from source and it still does not attempt to find lirc.
> >
> > Thanks
> > Malcolm
> >
> >> >> ----- Original Message -----
> >> >> From: "DanM" <dan at milkcarton.com>
> >> >> Sent: Tuesday, March 30, 2004 9:44 PM
> >> >>
> >> >>
> >> >> > do you have something like
> >> >> > begin
> >> >> >   prog = xine
> >> >> >   button = Play
> >> >> >   config = Play
> >> >> > end
> >> >> >
> >> >> > in your .lircrc file?
> >> >> >
> >> >> > -dan
> >> >
> >> >>>----- Original Message -----
> >> >>>From: "malcolm" <mythtv at lds.dyndns.org>
> >> >>>Sent: Tuesday, March 30, 2004 10:48 PM
> >> >>
> >> >> Dan, I have that type of .lircrc file in ~ but I noticed while
> >> watching
> >> >> /var/log/lircd that Xine is not even connecting to the lircd daemon.
> >> >> When
> >> > I
> >> >> fire up Myth or mplayer I see a "client connected" in
/var/log/lircd.
> >> >> I'm
> >> >> using the default xine that came with Mandrake 10.0.  Is there a
> > command
> >> >> line option to tell Xine to use lirc?
> >> >>
> >> >> Thanks
> >> >> Malcolm
> >> >
> >> > OK I got Myth's native lirc support working and I got lirc working
> >> with
> >> > mplayer like this:
> >> > mplayer -lircconf ~/.mythtv/lirc-mplayer (used google to figure out
> >> > contents
> >> > of lirc-mplayer)
> >> >
> >> > Xine however is not even connecting to lircd.  I can check
> > /var/log/lircd
> >> > and check that.  I finally decided perhaps my xine that comes with
> >> > Mandrake
> >> > 10.0 might not be compiled with lirc support.  So I downloaded
> >> xine-lib
> >> > and
> >> > xine-gui source and compiled my own.  While compling xine-gui I got
> >> this
> >> > while running ./configure
> >> >
> >> > checking for lirc_init in -llirc_client... yes
> >> > checking lirc/lirc_client.h usability... yes
> >> > checking lirc/lirc_client.h presence... yes
> >> > checking for lirc/lirc_client.h... yes
> >> > checking for "/lib/liblirc_client.a"... no
> >> > checking for "/usr/lib/liblirc_client.a"... no
> >> > checking for "/usr/local/lib/liblirc_client.a"... yes
> >> >
> >> > Now that leads me to believe xine has found all the lirc libraries
and
> >> > will
> >> > compile with lirc support right?
> >> > "./configure --help" only shows an option to disable compiling lirc
> >> > support.
> >> > Nothing to enable it.
> >> > Yet even after compiling my own xine-lib and xine-gui it still does
> >> not
> >> > even
> >> > connect to the lircd and I see no traces of it in the logs
> >> > (/var/log/lircd).
> >> >
> >> > I also saw on the web that if you get errors about lirc when starting
> >> up
> >> > Xine that you can use -L to disable support for it.  So I shutdown
> >> lircd
> >> > and
> >> > rmmod lirc_i2c and lirc_dev.  Now I have NO lirc stuff running.  I
> >> fire
> > up
> >> > Xine and no errors or complaints about lirc not been there.
> >> >
> >> > I'm at a loss here.  What's the trick to xine and lirc?
> >> >
> >> > Thanks
> >> > Malcolm
> >> >
> >> > _______________________________________________
> >> > mythtv-users mailing list
> >> > mythtv-users at mythtv.org
> >> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >> >
> >> >
> >>
> >
> >
>
> --------------------------------------------------------------------------
--
> > ----
> >
> >
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >
> >
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>

_______________________________________________
mythtv-users mailing list
mythtv-users at mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users




Bausch & Lomb
150 Years of Perfecting Vision, Enhancing Life (TM)






EMAIL DISCLAIMER 

Please Note: The information contained in this message may be privileged and
confidential, protected from disclosure, and/or intended only for the use of
the individual or entity named above. If the reader of this message is not
the intended recipient, or an employee or agent responsible for delivering
this message to the intended recipient, you are hereby notified that any
disclosure, distribution, copying or other dissemination of this
communication is strictly prohibited. If you received this communication in
error, please immediately reply to the sender, delete the message and
destroy all copies of it.

Thank You