Recherche avancée

Sur d’autres sites (9941)

• Is it possible to get ffmpeg-concat running in windows ?

  7 décembre 2018, par jem

  I’d like to use ffmpeg-concat running on a Windows server as a CLI. I’ve tried using nexe and pkg to creat an executable but both come up with (different) errors when I try it. This is my first foray into node.js, so apologies for noob questions.

  Has anyone else managed to do this, or can point me to a Windows build somewhere ?

• How to compile FFmpeg with bash on Windows 10 ?

  10 août 2017, par user2980183

  In the Creators Update (1703), the Windows 10 bash linux (WSL) can run native windows tools. So, under Windows 10, you can now compile FFmpeg with Visual Studio and the required linux utilities, natively, without having to install MinGW or other interop crap software.

  Here is how I tried to compile FFmpeg (using MSVC 2017 toolchain) :

  • I started the bash shell from "Developer Command Prompt for VS 2017" to set PATH variable to find the MSVC compiler/linker.

  • I installed the "make" tool with the following command : "sudo apt-get install make".

  • To call Windows program from the bash shell, I have to type the command with its .exe extension. So, I must adapt the "configure" and "compat/windows/makedef" files to add ".exe" at the end of "cl", "link" (no confusion possible with the /usr/bin/link), "dumpbin" and "lib" executables :

  configure

  cl_major_ver=$(cl 2>&1 | sed -n 's/.*Version \([[:digit:]]\{1,\}\)\..*/\1/p')
  
      if [ -z "$cl_major_ver" ] || [ $cl_major_ver -ge 18 ]; then
  
          cc_default="cl.exe"
  
      else
  
          cc_default="c99wrap cl"
  
      fi
  
      ld_default="link.exe"
  
      nm_default="dumpbin.exe -symbols"
  
      ar_default="lib.exe"

  compat/windows/makedef

  lib.exe -out:${libname} $@ >/dev/null
  
  
  
  arch=$(dumpbin.exe -headers ${libname} |
  
     tr '\t' ' ' |
  
     grep '^ \+.\+machine \+(.\+)' |
  
     head -1 |
  
     sed -e 's/^ \{1,\}.\{1,\} \{1,\}machine \{1,\}(\(...\)).*/\1/')
  
  
  
  dump=$(dumpbin.exe -linkermember:1 ${libname})

  I hope the FFmpeg build tool chain will be adapted in the future to support natively compiling on bash on Windows...

  • If you want to set an absolute path for YASM in the "configure", you have to use the following pattern /mnt/[letter_partition]/path/yasm.exe.

  ./configure --toolchain=msvc --yasmexe='/mnt/e/Home/Important/Development/Toolkit/Tools/yasm-1.3.0-win32.exe' [all other settings you need]

  • The make command should generate the lib as expected.

  • I tried to type make install but I get the following error :
    No rule to make the target "libavutil\x86\x86util.asm", needed for "libavutil/x86/cpuid.o".

  I don’t know what is wrong...

  As you can see, building FFmpeg on bash under Windows is not very developer friendly yet. Compiling FFmpeg in Windows should be as easy as Linux. Do you know if there is an easier way to proceed ? Do you know if this compilation scenario will be officially supported in next versions of FFmpeg (I don’t find any roadmap) ?

  Thanks.

• Anomalie #2477 (Nouveau) : Plugin activé mais pas activé

  8 janvier 2012, par Maïeul Rouquette

  Sous SPIP 3 SVN 18892, avec le plugins squelettes_documentation et tout les plugins requis pour son fonctionnement, lors de son activation, j’obtenais : activation du plugin « Squelette Documentation » (version : 002.000.000) s’est correctement déroulée L’installation du plugin « Squelette (...)