Re: [vdr] plugin loading
Ludwig Nussel wrote: e9hack wrote: Udo Richter wrote: e9hack wrote: I've selected some plugins for loading. It exist ca. 100 plugins in the vdr lib directory. Does vdr load only the selected plugins or all plugins? There is no common way how the plugins get selected for loading. VDR itself does not load plugins unless instructed. (except for --version and --help) Plugins get loaded by the -P or --plugin command line option, by modifying the runvdr script that is part of the VDR sources, or by distribution dependent load mechanisms in case you're using pre-built packages. It seems, it is a problem of the runvdr script from suse. The script prepares a list of installed and missing plugins from a list of selected plugins. The script does some bogus things, if it exist an plugin with wrong import entries. What kind of bogus things do you mean? The script runs vdr --version to filter out obviously not working plugins, that's all. Something is wrong in processplugins from runvdr (suse 10.1). 'VDR_PLUGINS' is set to 'dvd femon epgsearch lcdproc reelchannelscan wirbelscan atmo'. If my buggy image plugin does exist in the lib directory, 'missing_plugins' is set to 'dvd wirbelscan femon lcdproc epgsearch' and 'installed_plugins' is set to 'reelchannelscan atmo'. If the buggy plugin doesn't exist in the lib directory, 'missing_plugins' is empty and 'installed_plugins' is set with the content from 'VDR_PLUGINS'. - Hartmut ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] plugin loading
e9hack wrote: Something is wrong in processplugins from runvdr (suse 10.1). 'VDR_PLUGINS' is set to 'dvd femon epgsearch lcdproc reelchannelscan wirbelscan atmo'. If my buggy image plugin does exist in the lib directory, 'missing_plugins' is set to 'dvd wirbelscan femon lcdproc epgsearch' and 'installed_plugins' is set to 'reelchannelscan atmo'. If the buggy plugin doesn't exist in the lib directory, 'missing_plugins' is empty and 'installed_plugins' is set with the content from 'VDR_PLUGINS'. Does vdr --version output anything unusal that could confuse the awk script inside runvdr? cu Ludwig -- (o_ Ludwig Nussel //\ SUSE LINUX Products GmbH, Development V_/_ http://www.suse.de/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] plugin loading
Udo Richter wrote: e9hack wrote: I've selected some plugins for loading. It exist ca. 100 plugins in the vdr lib directory. Does vdr load only the selected plugins or all plugins? There is no common way how the plugins get selected for loading. VDR itself does not load plugins unless instructed. (except for --version and --help) Plugins get loaded by the -P or --plugin command line option, by modifying the runvdr script that is part of the VDR sources, or by distribution dependent load mechanisms in case you're using pre-built packages. It seems, it is a problem of the runvdr script from suse. The script prepares a list of installed and missing plugins from a list of selected plugins. The script does some bogus things, if it exist an plugin with wrong import entries. - Hartmut ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] plugin loading
e9hack wrote: Udo Richter wrote: e9hack wrote: I've selected some plugins for loading. It exist ca. 100 plugins in the vdr lib directory. Does vdr load only the selected plugins or all plugins? There is no common way how the plugins get selected for loading. VDR itself does not load plugins unless instructed. (except for --version and --help) Plugins get loaded by the -P or --plugin command line option, by modifying the runvdr script that is part of the VDR sources, or by distribution dependent load mechanisms in case you're using pre-built packages. It seems, it is a problem of the runvdr script from suse. The script prepares a list of installed and missing plugins from a list of selected plugins. The script does some bogus things, if it exist an plugin with wrong import entries. What kind of bogus things do you mean? The script runs vdr --version to filter out obviously not working plugins, that's all. cu Ludwig -- (o_ Ludwig Nussel //\ SUSE Labs V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] plugin loading
e9hack schrieb: Hi, I've selected some plugins for loading. It exist ca. 100 plugins in the vdr lib directory. Does vdr load only the selected plugins or all plugins? It exist one plugin with a missing import symbol in the lib directory. This plugin is not selected for loading. The vdr does only load two plugins instead of the select amount and I see an error message from a buggy plugin: Mar 26 00:24:28 very-new-darkstar vdr: [27019] ERROR: /usr/lib/vdr/libvdr-image.so.1.4.5: undefined symbol: av_free Mar 26 00:24:28 very-new-darkstar vdr: [27027] VDR version 1.4.6 started Mar 26 00:24:28 very-new-darkstar vdr: [27027] loading plugin: /usr/lib/vdr/libvdr-reelchannelscan.so.1.4.5 Mar 26 00:24:28 very-new-darkstar vdr: [27027] loading plugin: /usr/lib/vdr/libvdr-atmo.so.1.4.5 Mar 26 00:24:28 very-new-darkstar vdr: [27027] loading /etc/vdr/setup.conf ... The image plugin is not selected for loading. Does vdr load all plugins from the lib directory and wast many resources? - Hartmut Its prety easy, vdr does not load all plugins but only the ones which you select in the runvdr , so vdr -Pimage should start up vdr only with image plugin. Maybe someone else can shed some more light on this. Some more details about how you have selected the plugins might help though (start option or which runvdr or shich distro etc pp, something that might shed some light on this. Kind Regards Steffen ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
