Re: [vdr] Plugin compiler arguments / Make.config

2009-12-06 Thread Klaus Schmidinger
On 28.10.2009 20:44, Udo Richter wrote: > On 28.10.2009 09:01, Andreas Mair wrote: >> I wonder why no other plugin authors shared there opinion and how they >> fix it. As I understand it every plugin must be changed whenever VDR >> introduces changes in that area and if the VDR compiling user doesn

Re: [vdr] Plugin compiler arguments / Make.config

2009-10-28 Thread Udo Richter
On 28.10.2009 09:01, Andreas Mair wrote: I wonder why no other plugin authors shared there opinion and how they fix it. As I understand it every plugin must be changed whenever VDR introduces changes in that area and if the VDR compiling user doesn't use (and adopt) Make.config. I guess this o

Re: [vdr] Plugin compiler arguments / Make.config

2009-10-28 Thread Andreas Mair
Hi! Sorry for digging out that old posting, but for my plugin I ran into that problem too. I wonder why no other plugin authors shared there opinion and how they fix it. As I understand it every plugin must be changed whenever VDR introduces changes in that area and if the VDR compiling user does

[vdr] Plugin compiler arguments / Make.config

2009-07-10 Thread Frank Schmirler
Hi there, since vdr-1.7.3, VDR is compiled with the additional arguments -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE Plugins should be compiled with the same arguments as otherwise one might get unresolved symbols when loading the plugin. Consistently, in vdr-1.7.4 these defin