Recherche avancée

Sur d’autres sites (10383)

• FFmpeg WASM Custom build : defining custom flags

  4 avril, par Ettur

  I wish to create custom ffmpeg.wasm build

  


  Now the official GUIDE show four commands "make dev" "make prd" etc

  


  So I cloned THE REPO and ran "make prd". It did build, but obviously, this build was with default settings, whatever exactly they made be.

  


  So pardon my stupidity, as I cannot figure out how / where / what do I edit to set the custom flags about what I want to be included / excluded in the build ?

  


• doc/filters : add missing palette* options

  9 septembre 2016, par Lou Logan

  doc/filters : add missing palette* options
  Introduced in b7e78c7 and 93ae68d.
  Fixes #5835.
  The paletteuse debug options that are not part of the official API are
  
  not included (debug_kdtree and color_search).
  Signed-off-by : Lou Logan <lou@lrcd.com>
  

  • [DH] doc/filters.texi

• How to compile ffmpeg for Windows statically with MSYS2 environment ?

  17 janvier 2024, par username

  I want to build myself standalone statically linked ffmpeg binaries for Windows from official git source code with MSYS2 environment tools. But every time I get .exe file dynamically linked to mingw libraries that crashes with "The application was unable to start correctly (0xc000007b)" error even if I put required libbz2-1.dll, libiconv-2.dll and libwinpthread-1.dll libraries in it's folder.

  



  I'm running MSYS2 environment with

  



  msys2_shell.cmd -mingw64


  



  line, and use mingw64/mingw-w64-x86_64-gcc 8.2.1+20181214-1 compiler package. Then I run ./configure with

  



  ./configure --pkg-config-flags=--static --disable-shared --enable-static


  



  line - the best options I have googled at all my efforts. Then proceed with general

  



  make
make install


  



  sequence.

  



  As a result, I get binaries that run smoothly in MSYS2 environment itself, but when I run it from host Windows explorer or cmd, first of all it ask for libbz2-1.dll, libiconv-2.dll and libwinpthread-1.dll libraries and when I put them in binaries' folder, they crash with "The application was unable to start correctly (0xc000007b)" error.

  



  I've asked about this case at official https://ffmpeg.zeranoe.com/forum/viewtopic.php?f=5&t=6439 forum but still have no response for already 5 days.

  



  Regarding dynamic linking libraries somehow I got bandaid solution with removing *.dll.a files from mingw64\x86_64-w64-mingw32\lib folder. But it looks not very clean for me. I wish to know if it is possible to do static linkage with some compiler/make/linker parameters or with editing ./configure or Makefile files somehow ?

  



  Also 0xc000007b error still remaining.

  



  I've managed to have desired result with media-autobuild_suite based on the same MSYS2 environment, so I know it is possible to do this somehow. But I'm very new to all this *nix things so don't understand it's bash script at all, not to mention it is pretty sophisticated by itself. The only thing I see it's producing correct ffmpeg executables running under native Windows environment not requiring dlls listed above.

  



  According to all guides in internet I found at the moment, I should get standalone Windows executables with this toolset, but it just don't work and I'm stuck. Please, help.