Recherche avancée

Sur d’autres sites (5083)

• New FATE Test Coverage System

  10 août 2010, par Multimedia Mike — FATE Server

  I’ve been feeling a bit scattered for the last week since I was fired from my volunteer position as the FFmpeg QA manager, wondering if there is anything I should attempt to do with the project. It can’t be denied that the new system is working well. But one area I’ve wondered about is test coverage.

  Under my old regime I tracked test coverage as a wiki page which was a highly flawed method— tedious and error-prone. There are those 2 adjectives again— tedious and error-prone ; whenever I see those, I search for automation methods. I think that might be more plausible thanks to the new FATE’s tighter integration with the FFmpeg build system.

  I don’t think anyone is working on this problem so I wanted to toss out a brainstorm :

  1. First, run ’ffmpeg -formats’, ’ffmpeg -codecs’, etc. and parse the output to collect a list of all the features (full list : -formats, -codecs, -bsfs, -protocols, -filters, -pix_fmts). Transform these lists into a standardized list of features, e.g., "DEVSD  ffvhuff         Huffyuv FFmpeg variant" represents features ’decode-video-ffvhuff’, ’encode-video-ffvhuff’, ’ffvhuff-horizband’, and ’ffvhuff-dr1’.
  2. Next, tag each individual test spec with the features that it exercises. E.g., test ’fate-vqa-cc’ exercises features ’demux-wsvqa’, ’decode-video-vqavideo’, and ’decode-audio-adpcm_ima_ws’.
  3. Finally, compare the data from parts 1 and 2. Print a list of all the features that are not exercised in FATE.

  I think a lot of this could be implemented at the GNU make level. Then again, I’m no expert on GNU make syntax so I may be overestimating its capabilities. Or there might be simpler ways to automatically track test coverage stats based on the improved testing infrastructure.

• Android transplant FFmpeg, call libffmpeg.so function appears ffmpeg.c : 8 : error : undefined reference to 'avcodec_version'

  24 avril 2015, par user4827738

  I need to use FFmpeg on Android, I use the FFmpeg compiled [ffmpeg for
  android][1] got libffmpeg.so, I will put the NDK libffmpeg.so
  platforms\android-8\arch-arm\usr\lib and several in the same
  directory, the script file on the
  platforms\android-8\arch-arm\usr\include directory, and then
  reference the way I wrote on the network Android.mk file, call
  avcodec_version in C code () ; function, and then prompts ffmpeg.c : 8 :
  error : undefined reference to ’avcodec_version, please help me, I’m on
  windows7 and ubuntu 14.04 are compiled, without success，thank you very
  much !

  android.mk code content

  LOCAL_PATH := $(call my-dir)
  
  
  
  include $(CLEAR_VARS)
  
  PATH_TO_FFMPEG := $(LOCAL_PATH)/ffmpeg
  
  LOCAL_C_INCLUDE += $(PATH_TO_FFMPEG)
  
  LOCAL_STATIC_LIBRARIES := -lffmpeg
  
  LOCAL_MODULE    := ffmpeg
  
  LOCAL_MODULE    := hello-ffmpeg
  
  LOCAL_SRC_FILES := ffmpeg.c
  
  
  
  include $(BUILD_SHARED_LIBRARY)

  libffmpeg.so code calls the function

  #include 
  
  #include 
  
  #include 
  
  #include <libavcodec></libavcodec>avcodec.h>
  
  JNIEXPORT void JNICALL Java_cn_znv_ffmpeg_FFmpegNative_getVersion(JNIEnv * env, jobject obj){
  
  avcodec_version();
  
  }

  error message when ndk-build

  E:\EasyCam\HLS\FFmpeg01\jni>ndk-build "Compile thumb : hello-ffmpeg <= ffmpeg.c
  
  SharedLibrary  : libhello-ffmpeg.so
  
  D:/AndroidEditor/android/android-ndk-r9/toolchains/arm-linux-androideabi-4.6/pre
  
  built/windows-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.6/../../../../arm-li
  
  nux-androideabi/bin/ld.exe: E:/EasyCam/HLS/FFmpeg01//obj/local/armeabi/objs/hell
  
  o-ffmpeg/ffmpeg.o: in function Java_cn_znv_ffmpeg_FFmpegNative_getVersion:E:/Eas
  
  yCam/HLS/FFmpeg01//jni/ffmpeg.c:8: error: undefined reference to 'avcodec_version'
  
  
  
  collect2: ld returned 1 exit status
  
  make: *** [E:/EasyCam/HLS/FFmpeg01//obj/local/armeabi/libhello-ffmpeg.so] Error 1

• Package Hs-FFmpeg won't compile

  28 décembre 2014, par changeyourstrings

  I guess, I’m another victim of cabal hell.

  I am trying to install the Haskell FFmpeg Bindings via the according cabal query using GHC-7.8.3 on OS X 10.9 :

  cabal install hs-ffmpeg

  After getting all the necessary libraries (like libdc1394, libvorbis,..) and includes usable via pkg-config, I thought I would finally come to compiling the sources.

  The latest Hs-FFmpeg package from Hackage (v.0.3.4) has a upper bound concerning the version of the haskell base lib, demanding a version less than 4.
  I failed in trying to install two separate versions of base using cabal sandboxes.

  Then I read that patching the hs-ffmpeg’s cabal file might work. So I changed the upper bound for base from versions <4 to <5.

  After doing so, the cabal configure works nice and smooth, cause I silenced the base constraint part.

  I found another resource, that says a source patch would be necessary for a working hs-ffmpeg with Ghc 7. The patch seems to change some pointer types in a source file of the packing, nothing really exciting.

  After all that, I am trying to compile again, getting the following type errors :

  cabal install
  
  Resolving dependencies...
  
  Configuring hs-ffmpeg-0.3.4.1...
  
  Building hs-ffmpeg-0.3.4.1...
  
  Failed to install hs-ffmpeg-0.3.4.1
  
  Last 10 lines of the build log ( /Users/helgetur/.cabal/logs/hs-ffmpeg-0.3.4.1.log ):
  
  Codec.hsc:147:20: note: forward declaration of 'enum CodecID'
  
      hsc_type (enum CodecID);
  
                     ^
  
  /Library/Frameworks/GHC.framework/Versions/7.8.3-x86_64/usr/lib/ghc-7.8.3/template-hsc.h:60:10: note: expanded from macro 'hsc_type'
  
      if ((t)(int)(t)1.4 == (t)1.4)                          \

  Maybe one must strictly use the ffmpeg’s demanded base version ? How can I find the problem ?

  I am running out of ideas now, moreover there are almost no similar questions out there.