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#11161 - [ffmpeg] should provide /usr/include/ffmpeg/av*.h
Attached to Project:
Arch Linux
Opened by Nicolai Lissner (blackpenguin) - Saturday, 09 August 2008, 12:30 GMT
Last edited by Jan de Groot (JGC) - Sunday, 07 June 2009, 23:29 GMT
Opened by Nicolai Lissner (blackpenguin) - Saturday, 09 August 2008, 12:30 GMT
Last edited by Jan de Groot (JGC) - Sunday, 07 June 2009, 23:29 GMT
|
DetailsDescription:
many applications expect headers from /usr/include/libav*/ (like libavformat/avformat.h or libavcodec/avcodec.h) to be found in /usr/include/ffmpeg/ instead. Of course, it is possible to patch all these applications to use the (new?) header-locations, but maybe it would be better to provide them where expected? two examples that still expect the headers to be found in ffmpeg/: idjc and mocp, I'm sure there are many more builds like that. Symlinking everything found in /usr/include/libav*/* in /usr/include/ffmpeg/ should make these applications happy (and saves some time when building software) |
This task depends upon
Closed by Jan de Groot (JGC)
Sunday, 07 June 2009, 23:29 GMT
Reason for closing: Not a bug
Additional comments about closing: It's upstream decision to place the files there. ffmpeg hasn't been anywhere near API or ABI stable, so applications just need to adapt to the current version of ffmpeg.
Sunday, 07 June 2009, 23:29 GMT
Reason for closing: Not a bug
Additional comments about closing: It's upstream decision to place the files there. ffmpeg hasn't been anywhere near API or ABI stable, so applications just need to adapt to the current version of ffmpeg.
Having these issues fixed upstream would be by far the most ideal.
Also if these compatibility headers are provided, we won't be able to tell anymore which apps need to be updated?