[Ffmpeg-devel] Dll's with MinGW
lorenzk at gmx.net
Tue May 30 23:15:47 CEST 2006
Hello Matt et al,
thanks a lot, the patch works.
It's not perfect, as the libs and dlls still point to the .49, .50, .51
versions, but now the functions are listed in the libs.
Do you know, if there are any plans to tidy up the win32 build?
Matt Schuckmann wrote:
> I ran into this a couple of weeks ago and I got the attached patch from
> Diego Biurrun and it solved the problem by moving the .51 and .49
> and .50 to
> before the .lib and .dll. I think the problem is MS link doesn't
> know how to
> deal with files that are .51 etc.
> Perhaps this patch never got applied to the CVS tree.
> Matt S.
> -----Original Message-----
> From: ffmpeg-devel-bounces at mplayerhq.hu
> [mailto:ffmpeg-devel-bounces at mplayerhq.hu] On Behalf Of lorenzk at gmx.net
> Sent: Monday, May 29, 2006 2:57 PM
> To: ffmpeg-devel at mplayerhq.hu
> Subject: [Ffmpeg-devel] Dll's with MinGW
> after searching the archives, I found other people's questions on
> avcodec and avutil libraries under Windows/MinGW.
> I did successfully ffmpeg and the libs, but I get these files:
> The .51, .50, .49 files are binary identical to the .dll files.
> avcodec.dll references (uses) avutil.dll.49.
> avformat.dll references (uses) avutil.dll.49 and avcodec.dll.51.
> Is this (using the .51, .50, .49 files) by intention?
> When I look inside the lib files (with dumpbin.exe), I can see that there
> are no public symbols exported, besides the standard ones:
> __IMPORT_DESCRIPTOR_avcodec.dll (to me it looks like the ".dll" is wrong,
> because we then need a DLL avcodec.dll.dll)
> ?avcodec.dll_NULL_THUNK_DATA (again ".dll" that shouldn't be here)
> So it is no wonder that the libs cannot be used to automatically link
> against the DLLs.
> Please could somebody with insight shed a little light on this.
> ffmpeg-devel mailing list
> ffmpeg-devel at mplayerhq.hu
More information about the ffmpeg-devel