On Thu, Nov 30, 2017 at 2:43 PM, Carl Eugen Hoyos <[email protected]> wrote: > 2017-09-27 22:26 GMT+02:00 Hendrik Leppkes <[email protected]>: >> On Wed, Sep 27, 2017 at 10:11 PM, Mateusz <[email protected]> wrote: >>> W dniu 2017-09-27 o 17:40, Hendrik Leppkes pisze: >>>> On Wed, Sep 27, 2017 at 4:43 PM, Anonymous Maarten >>>> <[email protected]> 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. > > Given we are currently changing API and ABI, this shouldn't > be an issue. > But maybe there is a reason why .a files have an advantage? >
I think its actually somewhat beneficial to have different names for dynamic and static libraries, its easy to differentiate them. - Hendrik _______________________________________________ ffmpeg-devel mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
