[Libav-user] Dll Versioning

Alex Cohn alexcohn at netvision.net.il
Tue Oct 30 14:21:36 CET 2012

On 30 Oct 2012 15:01, "Mark Kenna" <mark.kenna at sureviewsystems.com> wrote:
> On 30 October 2012 10:55, Mark Kenna <mark.kenna at sureviewsystems.com>
>> On 30 October 2012 10:51, Nicolas George <nicolas.george at normalesup.org>
>>> Le nonidi 9 brumaire, an CCXXI, Mark Kenna a écrit :
>>> > I am trying to find a way of allowing my application to be able to
>>> > multiple versions of the FFMpeg DLL's at the same time.
>>> Why would you want to do that?
>>> The simplest solution to your problem is probably to find out how not to
>>> need it.
>>> Regards,
>>> --
>>>   Nicolas George
>> I need to do that because we constantly find ourselves having
FFMpeg-based modules which overwrite our .dll files with older versions
causing serious crashing. I just need to be able to stop "drop-ins" from
interfering with the version that we are running.
>> Thanks,
>> Mark.
> I have also explored the option of statically linking the libraries but
this is not possible in MSVC++ right? Surely there has to be a way to do
> Mark.

Have you read a similar recent discussion on stackoverflow(

Today zeranoe archives include version number in the dll names. Are you
using a different source of precompiled Windows binaries?

Anyway, it's good practise to install the DLLs in your app directory, next
to the executable that will load them, and not in a shared directory where
other applications could override them or be hit because your installation
overwrought the files they relied upon.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ffmpeg.org/pipermail/libav-user/attachments/20121030/597bd36d/attachment.html>

More information about the Libav-user mailing list