[FFmpeg-devel] Fix mingw name of .lib files
Diego Biurrun
diego
Wed Mar 5 08:58:41 CET 2008
On Wed, Mar 05, 2008 at 01:01:02AM -0300, Gonzalo Garramu?o wrote:
> M?ns Rullg?rd wrote:
> >
> > If memory serves, attempting to run a Windows application with dlls
> > missing, will result in a message telling the user exactly which dlls
> > are required. In the case libavcodec, that would be the versioned
> > name.
>
> *IF* you link against the versioned name (which is what I'm *trying* to
> do easily) but not what you are proposing by having the .lib name being
> unversioned.
>
> The whole issue is that I'm trying to automate the release and I can't
> because for linking with the microsoft compiler/mingw, you need to find
> the lib file but for release you need to ship the correct DLL. As the
> lib name has no useful version, how am I to ship the right DLL? Things
> will only get worse if, as you say, I need to support multiple versions.
> You are assuming versions just increase and you never have to support
> older versions. Every time I compile ffmpeg, the avcodec.lib gets
> overwritten. In a couple of months, I would then have no idea which
> version it belongs to anymore.
You should really look into static linking and/or BUILDSUF.
Diego
More information about the ffmpeg-devel
mailing list