![]() Note that Win32 builds in Visual Studio assume that you use 32-bit files from Zeranoe. The sample and instructions remain in good standing. UPDATE: The project in repository is upgraded to Visual Studio 2013 (older VS 2010 code) and checked against current Zeranoe builds. And your app will work from there: C:FFmpegAppRelease>FFmpegApp.exe This is when you extract the "Shared" archive, and copy DLLs from its bin to the directory of your binary. This will be sufficient to build the binary, and it will be dependent on av*.dll: You will extract "Dev" archive into dev subdirectory of Visual Studio project and you will add devinclude on the additional include path. _tprintf(_T("Trying avcodec_register_all. So, your Visual Studio project can be as simple as this ( browse full source here): extern "C" ![]() "Dev" archive has lib files which you can use in your project to link to them as well in a way that ffmpeg.exe does in shared archive. "Shared" archive has FFmpeg built with dynamic link to DLL libraries. On Zeranoe you will find archives like this: lib libraries that link into your binary. "Static" on Zeranoe means that libraries are statically linked into binaries like ffmpeg.exe. You have to use and redistribute the av*.dll dependent files with your binary to have it working. You built your project as per item 1 above. compile FFmpeg from source code into static libraries using non-Microsoft compiler, and then link to your Visual Studio project (mind the LGPL/GPL license in this case). ![]() lib/.dll files and your binary produced with Visual Studio will be dependent on av*.dll files
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |