Author
Topic: VDR integration - How to add plugins (Read 11257 times)

Yes, I built vdr-plugin-lcdproc from the sources. The steps are following:- download and unpack vdr-plugin-lcdproc sources and Debian patch from the Ubuntu site;- apply Debian patch to the plugin directory;- install VDR headers (vdr-dev) and a few development packages such g++, debian-helper, fakeroot etc;- go to plugin directory and run

dpkg-buildpackage -rfakerootAs result you should get vdr-plugin-lcdproc package. After installation of that plugin you should modify /etc/vdr/plugins/order.conf to put it on the bottom. Here is my order.conf:

What Debian patch? I haven't downloaded the vdr-plugin-lcdproc source yet, will it be obvious which patch when I do so?How do I "apply" the Debian patch, and where is the "plugin" directory?install VDR headers = sudo apt-get install vdr-dev? You say "a few development packages" and list a few - could you be more specific just the 3 you mention? How do I tell exactly which ones are needed?

Michael - thank you very much for the detailed instructions! I got all the way through to the dpkg-buildpackage command, and had a couple of packages it errored on, as you suggested. So I apt-get installed (dpatch and fakeroot).... these installed fine...

I have looked at that line in the file and have no idea why it is causing a permission denied error. As you can see, I even sudo -i first to be sure, but it does the same thing just from linuxmce and with a sudo in front of the command. I suggestions?

Silly me, didn't realise debian/rules was a folder/file, was reading it as a sentence! Fixed that up and built, but it comes up with more errors that I am ill-equiped to understand/debug!

The only clue I can see is it seems to be complaining about the directory name I created (vdrlcdproc) - looks like it might expect it to be different and is using it to locate a .orig file?? Not sure what it is expecting, so I will tell you what I did. I just created a directory called vdrlcdproc under the linuxmce home folder for the plugin. Then saw you talking about expanding the patch into /tmp. So I did that. Where should they both be and called? Is this what is confusing it?

OK, so I think I have tidied up the mess of folders and stuff I made, and started from scratch in the /tmp folder. This time I got it to go further, and it seems to have finished, with only a few warnings:

# If you like a fixed plugin order in your menu place the plugin base names# here. Remember that the first entry a plugin may get, starts at five in# VDR's OSD.## If you want a certain Plugin not to be loaded automatically at# vdr-startup, then you can simply write "-pluginname" in this file.## If you want to add commandline-options for a certain plugin, this file is# not the right place - you can add them in the file(s)# /etc/vdr/plugins/plugin.<pluginname>.conf - each option in one line

I rebooted LMCE and it seems TV is back again, although I don't know why. I edited the order.conf file and added xineliboutput and -lcdproc, restarted VDR (/etc/init.d/vdr stop then start) no difference, and when it starts it only mentions xineliboutput as a plugin (as before) even though xineliboutput wasn't even in the order.conf file originally. Removed the "-" sign and tried again, with the same results.

So TV is working again, but I cannot find any evidence that the lcdproc plugin is even there. I did a sudo find / -name vdr* | grep lcd and there are no files or directories at all that match.

Further back you said, "As result you should get vdr-plugin-lcdproc package. After installation of that plugin you should modify /etc/vdr/plugins/order.conf to put it on the bottom. Here is my order.conf:"

Do you mean building the plugin (ie dpkg-buildpackage...) is one step, but then there is another step to actually "install" the plugin? Of course now I have rebooted, all the stuff in the /tmp directory is gone .... so I'm assuming that I was supposed to copy some files out of it into another folder (a vdr folder somewhere).... is that right?

sudo dpkg -i <path_to_your_package>After that as I already mentioned you should modify your /etc/vdr/plugins/order.conf to load xineliboutput plugin first. You posted just default file with examples how to enable/disable plugins using order.conf. Just put there that code:

Michael - great, thanks! One last question before I go ahead ... from memory what I ended up with was a directory with a whole load of files in it (mostly the source files I originally downloaded I think). When you say <pathtoyourpackage> what type of file will it be? A .deb?

It'll be a while before you get up, so I will start the process again, and see if I can find a deb or something else that is obvious, in the meantime!Thanks again...

Quick related question - I have configured lcdproc (client) as well to display a couple of system screens (CPU/Memory/etc) - I can run it from the command line, but obviously this doesn't survive reboots. I know there are numerous ways to run things at startup (cron, scripts, etc) but I have no idea which is the best for this type of thing - where and how would you suggest I run lcdproc from during startup?

I have tried to complie a plugin to vdr v. 1.7.11. After updating the Make.config with the path to the v4l files i got rid of the: usr/include/vdr/dvbdevice.h:19:2: error: #error VDR requires Linux DVB driver API version 5.0 or higher!

But when i tried to load the plugin I got an error about binary incompabiltiy. Can someone point me in right direction.

All our plugins are based on source packages from eTobi with PATCHVARIANT=multipatch

If you have specific plugins you think are helpful for other people as well, feel free to open a feature request in trac. If the plugin in question has source packages available on etobi, chances are good that we will incorporate the package into our repo.