Awesome, thanks! On Thu, Nov 23, 2017 at 1:04 PM, Dave Plater <[email protected]> wrote:
> Fixed kodi, confirmed by email. Submitted sr#4048 > Dave > > On 11/21/17, Dave Plater <[email protected]> wrote: > > Kodi is made to build with it's internal (from github.com/xbmc/FFmpeg) > > ffmpeg until kodi 1.8x is released which has been rewritten to build > > with ffmpeg 3.4. > > It already builds with "internal" libdvdcss, libdvdnav and libdvdread. > > These have become a problem since the internal ffmpeg build. These > > libs are statically linked. > > See the bug references at the beginning of this thread. > > Dave > > > > On 11/21/17, Olaf Hering <[email protected]> wrote: > >> On Tue, Nov 21, Dave Plater wrote: > >> > >>> What I don't understand is none of these are related to ffmpeg and why > >>> tis wasn't a problem before. > >> > >> Before we try to force a different libffmpeg into kodi, it must be > >> checked > >> if the other libraries in the kodi process make some use of libffmpeg. > >> If they do, there will be most likely a runtime conflict and kodi must > >> be fixed to work with "any" libffmpeg. > >> > >> In case of no conflict it is likely easier to build a private ffmpeg in > >> %_libdir/ffmpeg3x and build kodi with RPATH pointing to that directory. > >> > >> > >> Olaf > >> > > > _______________________________________________ Packman mailing list [email protected] http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
