Recherche avancée

Sur d’autres sites (6994)

• Build x264 with error : signal.h not found

  12 février 2018, par John

  When I build x264 using the build script :

  #!/bin/bash
  
  NDK=/Local/Android/sdk/android-ndk-r16b
  
  
  
  PLATFORM=$NDK/platforms/android-26/arch-arm/
  
  TOOLCHAIN=$NDK/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64
  
  PREFIX=./android/arm
  
  
  
  function build_one
  
  {
  
   ./configure \
  
   --prefix=$PREFIX \
  
   --enable-static \
  
  --enable-pic \
  
   --host=arm-linux \
  
   --cross-prefix=$TOOLCHAIN/bin/arm-linux-androideabi- \
  
   --sysroot=$PLATFORM
  
  
  
    make clean
  
    make
  
    make install
  
  }
  
  
  
  build_one
  
  
  
  echo Android ARM builds finished

  But i always got an error :

  x264.c:40:20: fatal error: signal.h: No such file or directory
  
  #include 
  
                  ^

  compilation terminated.
   : recipe for target ’x264.o’ failed
  make : *** [x264.o] Error 1

• Portable YUV Drawing Context

  1er juin 2017, par Leif Andersen

  I have a stream of YUV data (from a video file) that I want to stream to a screen in real time. (Basically, I want to write a program that plays the video in real time.)

  As such, I am looking for a portable way to send YUV data to the screen. I would ideally like to use something portable so I don’t have to reimplement it for every major platform.

  I have found a few options, but all of them seem to have significant issues. They are :

  1. Use OpenGL directly, converting the YUV data to RGB. (And using the single quad for the whole screen trick.)

  This obviously won’t work because converting RGB to YUV on the CPU is going to be too slow for displaying images in real time.

  2. Use OpenGL, but use a shader to convert the YUV stream to RGB.

  This option is a bit better. Although the problem here is that (afaict), this will involve making two streams and splicing them together. It might work, but may have issues with larger resolutions.

  3. Instead use SDL, which has the option of creating a YUV context directly.

  The problem with this is I already am using a cross platform widget library for other aspects of my program (such as playback controls). As far as I can tell, SDL only opens up in its on (possibly borderless) window. I would ideally like my controls and drawing context to be in the same window. Which I can do with opengl, but not SDL.

  4. Use SDL, and also use something like Qt for the on screen widgets, use a message passing protocol to communicate between the two libraries. Have the (borderless) SDL window constantly move itself on top of the opengl window.

  While this approach is clever, it seems like the two windows could get out of sink easily making the user experience sub-optimal.

  5. Forget a cross platform library, do thinks OS specific, making use of hardware acceleration if present.

  This is a fine solution although its not cross platform.

  As such, is there any good way to draw YUV data to a screen that ideally is :

  1. Portable (at least to the major platforms).
  2. Fast enough to be real time.
  3. Allows other widgets in the same window.

• Building ffmpeg 3.3 with android-ndk-r14b

  23 mai 2017, par Priyo Chatterjee

  Changes made in configure file of ffmpeg :

  SLIBNAME_WITH_MAJOR='$(SLIBPREF)$(FULLNAME)-$(LIBMAJOR)$(SLIBSUF)'
  
  LIB_INSTALL_EXTRA_CMD='$$(RANLIB) "$(LIBDIR)/$(LIBNAME)"'
  
  SLIB_INSTALL_NAME='$(SLIBNAME_WITH_MAJOR)'
  
  SLIB_INSTALL_LINKS='$(SLIBNAME)'

  build_configure.sh

  #!/bin/bash
  
    ######################################################
  
  # Usage:
  
  # put this script in top of FFmpeg source tree
  
  # ./build_android
  
  # It generates binary for following architectures:
  
  # ARMv6
  
  # ARMv6+VFP
  
  # ARMv7+VFM-ïd16 (Tegra2)
  
  # ARMv7+Neon (Cortex-A8)
  
  # Customizing:
  
  # 1. Feel free to change ./configure parameters for more features
  
  # 2. To adapt other ARM variants
  
  # set $CPU and $OPTIMIZE_CFLAGS
  
  # call build_one
  
  ######################################################
  
  NDK=$HOME/Fame/android-ndk-r14b
  
  PLATFORM=$NDK/platforms/android-9/arch-arm/
  
  TOOLCHAIN=$NDK/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64
  
  function build_one
  
  {
  
  ./configure --target-os=linux \
  
    --prefix=$PREFIX \
  
    --enable-cross-compile \
  
    --arch=arm \
  
    --cc=$PREBUILT/bin/arm-linux-androideabi-gcc \
  
    --cross-prefix=$PREBUILT/bin/arm-linux-androideabi-4.9 \
  
    --nm=$PREBUILT/bin/arm-linux-androideabi-nm \
  
    --sysroot=$PLATFORM \
  
    --extra-cflags=" -O3 -fpic -DANDROID -DHAVE_SYS_UIO_H=1 -Dipv6mr_interface=ipv6mr_ifindex -fasm -Wno-psabi -fno-short-enums -fno-strict-aliasing -finline-limit=300 $OPTIMIZE_CFLAGS " \
  
    --disable-shared \
  
    --enable-static \
  
    --disable-everything \
  
    --enable-demuxer=mov \
  
    --enable-demuxer=h264 \
  
    --disable-ffplay \
  
    --enable-protocol=file \
  
    --enable-avformat \
  
    --enable-avcodec \
  
    --enable-decoder=rawvideo \
  
    --enable-decoder=mjpeg \
  
    --enable-decoder=h263 \
  
    --enable-decoder=h265 \
  
    --enable-decoder=mpeg4 \
  
    --enable-decoder=h264 \
  
    --enable-parser=h264 \
  
    --enable-parser=h265
  
    --enabled-network \
  
    --enable-zlib \
  
    --disable-avfilter \
  
    --disable-avdevice \
  
    --disable-yasm \
  
    --disable-ffmpeg
  
    --disable-ffprobe
  
    --disable-ffserver
  
    $ADDITIONAL_CONFIGURE_FLAG
  
  
  
  make clean
  
  make  -j4 install
  
  $PREBUILT/bin/arm-linux-androideabi-ar d libavcodec/libavcodec.a inverse.o
  
  $PREBUILT/bin/arm-linux-androideabi-ld -rpath-link=$PLATFORM/usr/lib -L$PLATFORM/usr/lib \
  
  -soname libffmpeg.so -nostdlib,noexecstack -Bsymbolic \
  
  --whole-archive --no-undefined \
  
  -o $PREFIX/libffmpeg.so libavcodec/libavcodec.a libavformat/libavformat.a \
  
  libavutil/libavutil.a libswscale/libswscale.a \
  
  $PLATFORM/usr/lib/libc.so $PLATFORM/usr/lib/libm.so \
  
  $PLATFORM/usr/lib/libz.so \
  
  $PLATFORM/usr/lib/libdl.so $PLATFORM/usr/lib/liblog.so \
  
  --dynamic-linker=/system/bin/linker \
  
  $PREBUILT/lib/gcc/arm-linux-androideabi/4.9/libgcc.a
  
  }
  
  
  
  #arm v6
  
  #CPU=armv6
  
  #OPTIMIZE_CFLAGS="-marm -march=$CPU"
  
  #PREFIX=./android/$CPU
  
  #ADDITIONAL_CONFIGURE_FLAG=
  
  #build_one
  
  
  
  #arm v7vfpv3
  
  CPU=armv7-a
  
  OPTIMIZE_CFLAGS="-mfloat-abi=softfp -mfpu=vfpv3-d16 -marm -march=$CPU "
  
  PREFIX=./android/$CPU
  
  ADDITIONAL_CONFIGURE_FLAG=
  
  build_one
  
  
  
  #arm v7vfp
  
  #CPU=armv7-a
  
  #OPTIMIZE_CFLAGS="-mfloat-abi=softfp -mfpu=vfp -marm -march=$CPU "
  
  #PREFIX=./android/$CPU-vfp
  
  #ADDITIONAL_CONFIGURE_FLAG=
  
  #build_one
  
  
  
  #arm v7n
  
  #CPU=armv7-a
  
  #OPTIMIZE_CFLAGS="-mfloat-abi=softfp -mfpu=neon -marm -march=$CPU -mtune=cortex-a8"
  
  #PREFIX=./android/$CPU
  
  #ADDITIONAL_CONFIGURE_FLAG=--enable-neon
  
  #build_one
  
  
  
  #arm v6+vfp
  
  #CPU=armv6
  
  #OPTIMIZE_CFLAGS="-DCMP_HAVE_VFP -mfloat-abi=softfp -mfpu=vfp -marm -march=$CPU"
  
  #PREFIX=./android/${CPU}_vfp
  
  #ADDITIONAL_CONFIGURE_FLAG=
  
  #build_one

  Error in the console I am getting :
  ./build_android.sh

  ./configure : 466 : ./configure : cannot create ffbuild/config.log : Directory nonexistent
  ./configure : 466 : ./configure : cannot create ffbuild/config.log : Directory nonexistent
  /bin/arm-linux-androideabi-gcc is unable to create an executable file.
  C compiler test failed.