[Wine] RFC: New dependency on FFmpeg?

Georg Bege georg at bege.email
Sat Aug 22 18:54:49 CDT 2015


Of course, I know this - but you can react on those errors on runtime.
Eg. disabling the decoding/encoding - inform the user etc.
It could be feasable, if static linking cannot be done due various
distribution conflicts... however as we also read in the mailing list

Maybe its better to just implement the encoder then...

Am 23.08.2015 um 01:45 schrieb Martin Gregorie:
> On Fri, 2015-08-21 at 10:39 +0200, georg at bege.email wrote:
>> Hi
>> I'd be curious, why wouldnt it be possible to dynamicly load ffmpeg 
>> library if existing in the system.
>> (via search path, ld path etc.)?
> I haven't tried to use ffmpeg, but I have written dynamically loaded
> libraries as part of a plugin system for an emulator. Both main program
> and libraries are C code for Linux. The program will compile and link
> easily enough if your code is compatible with the library function's
> prototype. However, if the function's interface doesn't match the
> prototype (which could be the case if the library was replaced with a
> later version and the caller was not recompiled) or there's a name
> clash between extern variable names, i.e. the same variable is defined
> in both library and calling program, then the library will load OK but
> you'll get a linkage failure at run time.
> Martin

Georg Bege
Mail: georg at bege.email
XMPP: therion at ninth-art.de
IRC: megaTherion @ Freenode

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://www.winehq.org/pipermail/wine-users/attachments/20150823/42e9fbac/attachment.sig>

More information about the wine-users mailing list