[Libav-user] Compiling dll and lib
ganeshmundhe007 at gmail.com
Wed Aug 22 00:49:30 EEST 2018
Thanks for reply Carl.
If you look up link https://trac.ffmpeg.org/wiki/CompilationGuide/WinRT under
*window 10 x64 *it says launch Launch *VS2015 x86 x64 Cross Tools Command
Thn use --arch=x86_64 --target_os=32 and MD flag in config.
I did the exact same. Everything sooms good.
Used these in x64 cpp console app , build well *no error.*
But when I run app, vcruntime140_app.dll missing error shows.
I checked, have latest version of vs2015 with vcruntime140.dll and console
app running fine, if I use ffmpeg dll downloaded from shared build >ffmpeg
download. But i want lgpl version that why manually compiling them.
Even tried changing target_os=64, same result.
App throws vcruntime140_app.dll missing error on execute.
If I use vs2015 Dev command prompt to launch msys2> compile dll,thn it
throws unresolved linking errors for all ffmpeg API used.
Thank and regards
On Tue 21 Aug, 2018, 2:13 PM Carl Eugen Hoyos, <ceffmpeg at gmail.com> wrote:
> 2018-08-21 8:35 GMT+02:00, ganesh mundhe <ganeshmundhe007 at gmail.com>:
> > For commercial use I'm compiling FFmpeg 4.0 for 64bit window application.
> > But when I use https://trac.ffmpeg.org/wiki/CompilationGuide/WinRT for
> > windows 10 x64, but this fails to complie from VS2015 x86 x64 cross tool
> > command prompt.
> It fails?
> You should not use cross-compilation if you compile on host x86 for target
> x86 or on host x86_64 for target x86 or target x86_64.
> > I'm able to compile using vs2015 Dev command prompt but those ddl gives
> > unresolved linking error no matter what configuration I use.
> You get an unresolved linking error?
> Would you like to tell us which error you get in what situation?
> Carl Eugen
> Libav-user mailing list
> Libav-user at ffmpeg.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Libav-user