Hi,<div><br></div><div>On top of that, there is the issue with libav, the fork of ffmpeg which is using the same library names, include directories, etc but changing APIs and IIRC even moving some functionality from one library to another.</div>
<div><br></div><div>I don't know if the reasons behind the fork were justified or not, but what is certain is it was executed in a very very unfriendly and dirty way, trying to harm and confuse as much as possible :-/</div>
<div><br><br><div class="gmail_quote">2011/6/22 Michael Jansen <span dir="ltr"><<a href="mailto:info@michael-jansen.biz">info@michael-jansen.biz</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi<br>
<br>
We have four different files of that style flying aroung in kde<br>
<br>
strigi/libstreamanalyzer/cmake/FindFFMPEG.cmake<br>
kdelibs/cmake/modules/FindFFmpeg.cmake<br>
kdemultimedia/cmake/modules/FindFFMPEG.cmake<br>
amarok/cmake/modules/FindFFmpeg.cmake<br>
<br>
They best is the kdelibs one. Some are plain out problematic. They for example<br>
look up their header with PATH_SUFFIX libavcodec but include with<br>
<libavcodec/avcodec.h> (kdemultimedia). which break the build for some of us.<br>
<br>
The others seem to stem from the fact that they need different parts of<br>
ffmpeg. amarok only looks for avcodec and avformat. kdemultimedia looks for<br>
swscale additionaly.<br>
<br>
I tried to clean up the stuff with the attached file. Please review. It uses<br>
the components approach.<br>
<br>
Questions: There seems to be no way to check for a ffmpeg version because it<br>
has no global one. Perhaps it is a bad idea to look for ffmpeg and instead<br>
provide one FindXYZ.cmake file for each component. For now i export the<br>
individual version so potential users can check themselve.<br>
<br>
There are some @QUESTION comments in that script.<br>
<br>
And i have a problem with macro_optional_find_package and the analog thing<br>
from strigi. They do not account for potential COMPONENT arguments to the<br>
required module. Another argument for a split find_package for each component?<br>
Without a solution to that problem this file is useless. All modules use the<br>
macros to find ffmpeg.<br>
<br>
Mike<br>
<br>
<br>_______________________________________________<br>
Kde-buildsystem mailing list<br>
<a href="mailto:Kde-buildsystem@kde.org">Kde-buildsystem@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-buildsystem" target="_blank">https://mail.kde.org/mailman/listinfo/kde-buildsystem</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Pau Garcia i Quiles<br><a href="http://www.elpauer.org">http://www.elpauer.org</a><br>(Due to my workload, I may need 10 days to answer)<br>
</div>