Recherche avancée

Sur d’autres sites (4721)

• FFMPEG android compile error

  11 octobre 2017, par Sujith Manjavana

  I’m trying to compile ffmpeg for android using ndk. os:ubuntu 13.10. I followed this tutorial. but when i run the build_android.sh it gives me the following errors-

  sujith@Vaio:~$ cd /home/sujith/ndk9d/sources/ffmpeg
  
  sujith@Vaio:~/ndk9d/sources/ffmpeg$ sudo chmod +x build_android.sh
  
  [sudo] password for sujith: 
  
  sujith@Vaio:~/ndk9d/sources/ffmpeg$ ./build_android.sh
  
  /home/sujith/sujith/ndk9d/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-         x86_64/bin/arm-linux-androideabi-gcc is unable to create an executable file.
  
  C compiler test failed.
  
  
  
  If you think configure made a mistake, make sure you are using the latest
  
  version from Git.  If the latest version fails, report the problem to the
  
  ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net.
  
  Include the log file "config.log" produced by configure as this will help
  
  solving the problem.
  
  Makefile:2: config.mak: No such file or directory
  
  Makefile:53: /common.mak: No such file or directory
  
  Makefile:93: /libavutil/Makefile: No such file or directory
  
  Makefile:93: /library.mak: No such file or directory
  
  Makefile:95: /doc/Makefile: No such file or directory
  
  Makefile:178: /tests/Makefile: No such file or directory
  
  make: *** No rule to make target `/tests/Makefile'.  Stop.
  
  Makefile:2: config.mak: No such file or directory
  
  Makefile:53: /common.mak: No such file or directory
  
  Makefile:93: /libavutil/Makefile: No such file or directory
  
  Makefile:93: /library.mak: No such file or directory
  
  Makefile:95: /doc/Makefile: No such file or directory
  
  Makefile:178: /tests/Makefile: No such file or directory
  
  make: *** No rule to make target `/tests/Makefile'.  Stop.
  
  Makefile:2: config.mak: No such file or directory
  
  Makefile:53: /common.mak: No such file or directory
  
  Makefile:93: /libavutil/Makefile: No such file or directory
  
  Makefile:93: /library.mak: No such file or directory
  
  Makefile:95: /doc/Makefile: No such file or directory
  
  Makefile:178: /tests/Makefile: No such file or directory
  
  make: *** No rule to make target `/tests/Makefile'.  Stop.

  here is my build_android.sh

  #!/bin/bash
  
  NDK=$HOME/sujith/ndk9d
  
  SYSROOT=$NDK/platforms/android-9/arch-arm/
  
  TOOLCHAIN=$NDK/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86_64
  
  function build_one
  
  {
  
   ./configure \
  
  --prefix=$PREFIX \
  
  --enable-shared \
  
  --disable-static \
  
  --disable-doc \
  
  --disable-ffmpeg \
  
  --disable-ffplay \
  
  --disable-ffprobe \
  
  --disable-ffserver \
  
  --disable-avdevice \
  
  --disable-doc \
  
  --disable-symver \
  
  --cross-prefix=$TOOLCHAIN/bin/arm-linux-androideabi- \
  
  --target-os=linux \
  
  --arch=arm \
  
  --enable-cross-compile \
  
  --sysroot=$SYSROOT \
  
  --extra-cflags="-Os -fpic $ADDI_CFLAGS" \
  
  --extra-ldflags="$ADDI_LDFLAGS" \
  
  $ADDITIONAL_CONFIGURE_FLAG
  
  make clean
  
  make
  
  make install
  
  }
  
  CPU=arm
  
  PREFIX=$(pwd)/android/$CPU 
  
  ADDI_CFLAGS="-marm"
  
  build_one

  my build_android.sh is located in ffmpeg source root directory.
  how to fix this ? please help me..

• FFMPEG library Integration unsuccess

  1er septembre 2017, par Alok Kumar Verma

  I’m stuck with the integration of the FFMPEG file. I’m using Android Studio 2.3.3

  I’ve followed this link and hence got to know how to do this but all I’m getting is a failure.

  Links

  1. How to integrate the FFMPEG in your android
  2. Integrating android FFMPEG

  Now I"ve my ndk installed in this path : /Users/alok/Library/Android/sdk/ndk-bundle

  And I’ve downloaded the newest version of the FFMPEG i.e., 3.3.3 unzipped it in the sources folder of ndk-bundle

  Now I’ve followed this and implemented everything as said.

  • Editing the Configure File using TEXTVIEW in my mac

  • Creating a file name build_android.sh and copy pasting the given code. However I’ve changed the NDK path in my case in the code the code is here

    NDK=/Users/alok/Library/Android/sdk/ndk-bundle
SYSROOT=$NDK/platforms/android-23/arch-arm/
TOOLCHAIN=$NDK/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64

  • Now opening the folder through terminal and then typing this command sudo chmod +x build_android.sh followed by this sudo ./build_android.sh

  The result is : No android name folder created inside under the folder FFMPEG 3.3.3 in this root i.e., /ndk-bundle/sources/ffmpeg 3.3.3/

  and the terminal shows this output :

  ./configure: line 3341: syntax error near unexpected token `2'

  ./configure: line 3341:

  DEPCMD='$(DEP$(1)) $(DEP$(1)FLAGS) $($(1)DEP_FLAGS) $< 2>/dev/null | sed -e "/^\#.*/d" -e "s,^[[:space:]]*$(@F),$(@D)/$(@F)," > $(@:.o=.d)''
Makefile:2: config.mak: No such file or directory
Makefile:67: /common.mak: No such file or directory
Makefile:114: /libavutil/Makefile: No such file or directory
Makefile:114: /library.mak: No such file or directory
Makefile:116: /doc/Makefile: No such file or directory
Makefile:206: /tests/Makefile: No such file or directory
make: *** No rule to make target /tests/Makefile'. Stop.

  Hence I’m not been able to move next due to this which creating a JNI folder and stuff. I’m a beginner with FFMPEG and want to integrate it.

  NOTE : I’ve already used this library in my gradle

  compile ‘com.writingminds:FFmpegAndroid:0.3.2’

  For easy approach and things are working fine too but due to the older version I’m getting wrong outputs, so need to update it and there is one way and this is the way to do it.

• 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.