[FFmpeg-devel] Create .lib static libraries on Windows instead of .a libraries (using MSVC compiler)

Anonymous Maarten anonymous.maarten at gmail.com
Thu Sep 28 00:24:40 EEST 2017

The current situation is inconsistent.
It creates .lib/.dlls files for dynamic libraries and .a files for
static libraries.
This complicates e.g. detecting ffmpeg using cmake needlessly.
Changing this behavior would be a net gain.

I would also be happy if there would be a (configure) switch to
manually set the pre/suffix.


On 27 September 2017 at 22:26, Hendrik Leppkes <h.leppkes at gmail.com> wrote:
> On Wed, Sep 27, 2017 at 10:11 PM, Mateusz <mateuszb at poczta.onet.pl> wrote:
>> W dniu 2017-09-27 o 17:40, Hendrik Leppkes pisze:
>>> On Wed, Sep 27, 2017 at 4:43 PM, Anonymous Maarten
>>> <anonymous.maarten at gmail.com> wrote:
>>>> Hey,
>>>> Building the static ffmpeg library using vcpkg is currently broken [1][2].
>>>> This is mainly due to the fact that the built static libraries are .a files
>>>> with lib prefixes.
>>>> The attached patch sets the lib prefix to "" and the lib suffix to ".lib".
>>>> Tested by building ffmpeg using vcpkg and Visual Studio 2017 Community
>>>> Edition on Windows 10.
>>>> The resulted libraries link correctly to my application.
>>> This would break the workflow for everyone that is currently working
>>> with the current names, however.
>> For gcc it breaks nothing (it still makes lib...a files), for msvc it is improvement.
>> Is there any person happy with lib...a names for lib in msvc?
> It doesn't really matter if you're happy with it or not, if you change
> it stuff will still break.
> - Hendrik
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

More information about the ffmpeg-devel mailing list