[vdr] vdr-1.7.41: what's new way to run vdr out of it's sourcedir?
Hi, vdr doesn't copy plugins to PLUGINS/lib. Is there a way to get the old behaviour back? First look I couldn't find nothing in vdr's HISTORY file. Regards Halim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.41: what's new way to run vdr out of it's sourcedir?
Hi, Am 17.03.2013 09:20, schrieb Halim Sahin: Hi, vdr doesn't copy plugins to PLUGINS/lib. Is there a way to get the old behaviour back? First look I couldn't find nothing in vdr's HISTORY file. I think make LCLBLD=1 should do it. Lars. Regards Halim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.41: what's new way to run vdr out of it's sourcedir?
On 17.03.2013 09:20, Halim Sahin wrote: Hi, vdr doesn't copy plugins to PLUGINS/lib. Is there a way to get the old behaviour back? First look I couldn't find nothing in vdr's HISTORY file. From the INSTALL file: Configuration files: There are several configuration files that hold information about channels, remote control keys, timers etc. By default these files are spread around the system according to the FHS (File system Hierarchy Standard). If you prefer to have VDR built to run locally under the VDR source tree, you can copy the file Make.config.template to Make.config and set the parameter LCLBLD=1. If you also want to have all data files under one single directory, set ONEDIR=1 in Make.config. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.41: what's new way to run vdr out of it's sourcedir?
Am 17.03.2013 09:51, schrieb Lars Hanisch: Am 17.03.2013 09:20, schrieb Halim Sahin: vdr doesn't copy plugins to PLUGINS/lib. Is there a way to get the old behaviour back? I think make LCLBLD=1 should do it. Mostly, but YMMV. Some plugins may not support it. From my builds yesterday, the most recent xineliboutput Makefile seems stuck between the versions, not copying 'the old way' to ../../../PLUGINS/lib any more, and not adhering 'the new way' LCLBLD request to do it. Also, in case ./PLUGINS/lib is not the final destination, you'll loose the ability to set default search paths for all the libs, so you have to specify them on command line. The alternative, doing an make install DESTDIR=/tmp/foo/ and picking files from there may fail because of too many broken plugin Makefiles. (at least the last time I've tried) Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
