Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#38306 - [deadbeef] Enable ffmpeg support in 0.6.0
Attached to Project:
Community Packages
Opened by Vorbote (vorbote) - Sunday, 29 December 2013, 12:09 GMT
Last edited by Lukas Fleischer (lfleischer) - Friday, 31 January 2014, 20:39 GMT
Opened by Vorbote (vorbote) - Sunday, 29 December 2013, 12:09 GMT
Last edited by Lukas Fleischer (lfleischer) - Friday, 31 January 2014, 20:39 GMT
|
DetailsAlthough ffmpeg support has been enabled in the build() section of the PKGBUILD, it wasn't included in the makedepends section, therefore the plugin wasn't created. The attached file provides a patch to correct it.
|
This task depends upon
enable_ffmpeg.patch
ffmpeg.c:859:2: warning: #warning FFMPEG-0.11 and higher does not expose register_protocol API, which means that it cant work with MMS and HTTP plugins. If you need this functionality, please downgrade FFMPEG to version 0.10 or less, and rebuild the FFMPEG plugin [-Wcpp]
#warning FFMPEG-0.11 and higher does not expose register_protocol API, which means that it cant work with MMS and HTTP plugins. If you need this functionality, please downgrade FFMPEG to version 0.10 or less, and rebuild the FFMPEG plugin
Does that mean some ffmpeg functionality is disabled for MMS and HTTP only?
And what about using ffmpeg-compat, ie. 'PKG_CONFIG_PATH+="/usr/lib/ffmpeg-compat/pkgconfig" configure [..]'
to get ffmpeg functionality for all plugins?