Hi,
I had a similar situation with xine plugin and finally I decided to use only e-tobi repositories (more plugins than in ubuntu builds) and softdevice plugin instead of xinelib plugin compiled from source in the following way:
apt-get source vdr-plugin-softdevice apt-get build-dep vdr-plugin-softdevice
cd "directory with plugin source" fakeroot debian/rules binary
It build vdr-plugin-softdevice-***.deb and it can be successfully use with vdr. But remember, use ONLY e-tobi repositories. You can check version in synaptic. In the same way you can build any vdr plugin from e-tobi repositories:
## VDR sources deb http://e-tobi.net/vdr-experimental/ etch base addons vdr-standard deb-src http://e-tobi.net/vdr-experimental/ etch base addons vdr-standard
Good luck,
Yarema
Leo Márquez написав(ла):
Hi,
I'm trying to set vdr building the packages from the e-tobi source packages. I'm doing this because I want to run vdr as streamdev client, with no dvb card in the client system. The e-tobi source I'm using is:
deb-src http://e-tobi.net/vdr-experimental etch base addons vdr-multipatch
The problem I have is that if I do:
sudo apt-get build-dep vdr-plugin-xineliboutput
The system says me that any version of the libxine-dev package can satisfy the xineliboutput dependencies. If I ignore the message and try to build the .deb packages (satisfying manually the dependences) there is a moment that apt ask me to update the vdr package. At this point I am a bit confused because I understand that this is a conflict between my e-tobi installed vdr and the ubuntu hardy vdr package.
My goal on this is get a streamdev client vdr box with xineliboutput output.
Could anyone advise me to acquire my objective?
Thank you.
Leo
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr