Closed tkurbad closed 11 years ago
Hmm, ... I'm using vdr 1.7.35 and i don't see this behaviour.
That's strange. Maybe it's Gentoo's fault. They tend to do funny things with vdr in order to be able to compile plugins externally...
Just a small addition: I don't see that same behaviour for manio's vdr-dvbapi plugin: https://github.com/manio/vdr-plugin-dvbapi
He incorporated both the pre-1.7.34 and the post-and-including-1.7.34 built styles into his Makefile.
Do you see any chance to do the same for the xvdr plugin?
I don't want to have a mixed makefile. I used the VDR template to create the new makefile and from my point of view it seems to be correct.
I see your point. So, I'll try to investigate this further as soon as I have the time...
The Gentoo eclass has been adapted to the build system changes. I'm now running VDR 1.7.42 with vdr-plugin-xvdr compiled from the master branch.
Alex,
it took me a while to figure that, but it seems vdr 1.7.35 has changed the plugin build system again and/or reverted the changes from 1.7.34. :-(
That, confusingly, leads to a non-operating plugin for 1.7.35 if compiled from the master branch, while compiling and running from the 'master-pre-vdr-1.7.34' works just fine.
In the former case, compilitian also succeeds, only vdr crashes while trying to initialize the plugin. The latter, as said, works fine in every regard.
Can someone confirm this behaviour?
Best, Torsten