I have installed 1.5.17 (i think) of vdr (from the experimental apt repository) however I can't get xineliboutput compiled as it's complaining that it can't find a valid libxine. It looks like the dependencies are quite specific in what they want.
Hi,
Just tackled with this one myself... at least if you used the e-tobi repositories. There was a strange requirement for the library version, I think it was something like libxine => 1.1.12 libxine << 1.1.13. If anyone knows what is so terribly wrong with later libxine, please let me know... What I did, was I just edited out the latter requirement from the debian/control file, and a couple of others (can't remember what they were, but there were about 4-5 files in the debian directory with the requirement setting). Compilation went well with libxine 1.1.17 and the plugin and the frontends work fine.
I demand that Timo Laitinen may or may not have written...
[snip]
Just tackled with this one myself... at least if you used the e-tobi repositories. There was a strange requirement for the library version, I think it was something like libxine => 1.1.12 libxine << 1.1.13.
Highly unlikely.
That *is* the general form, though, and it's to do with the name of xine-lib's plugins directory and how the plugin build scripts get the directory name. As of 1.1.11, though, things will start getting better in this respect since the naming of the directory will use the same information that libtool uses for generating the library soname, and directories for older versions (which match the same soname major number) will be looked in.
It's not *perfect* (that would involve use of details of which exported symbols were added when to decide exactly where the plugin should go), but it's a lot better than having to rebuild just because of a newer xine-lib :-)
[snip]
Compilation went well with libxine 1.1.17 and the plugin and the frontends work fine.
1.1.17? Did you get that from... I don't know, probably late next year? :-)
-
Darren Salt -
Timo Laitinen