Recherche avancée

Sur d’autres sites (9782)

• avformat : introduce AVFormatContext io_close2 which returns an int

  30 novembre 2021, par Marton Balint

  avformat : introduce AVFormatContext io_close2 which returns an int
  Otherwise there is no way to detect an error returned by avio_close() because
  
  ff_format_io_close cannot get the return value.
  Checking the return value of the close function is important in order to check
  
  if all data was successfully written and the underlying close() operation was
  
  successful.
  It can also be useful even for read mode because it can return any pending
  
  AVIOContext error, so the user don't have to manually check AVIOContext->error.
  In order to still support if the user overrides io_close, the generic code only
  
  uses io_close2 if io_close is either NULL or the default io_close callback.
  Signed-off-by : Marton Balint <cus@passwd.hu>
  

  • [DH] doc/APIchanges
  • [DH] libavformat/avformat.h
  • [DH] libavformat/dashenc.c
  • [DH] libavformat/fifo.c
  • [DH] libavformat/hlsenc.c
  • [DH] libavformat/internal.h
  • [DH] libavformat/options.c
  • [DH] libavformat/segment.c
  • [DH] libavformat/tee.c
  • [DH] libavformat/utils.c
  • [DH] libavformat/version.h

• Swift framework project with internal C module - Undefined symbols for architecture arm64

  29 mars 2020, par Phạm Phi Phúc

  I’m creating Swift framework project using FFmpeg module internally.

  Steps are :

  1. Download source of FFmpeg from official website.
  2. Build it by build script here : https://github.com/kewlbear/FFmpeg-iOS-build-script
  3. Copy built file to project
  4. Create file module.modulemap, it’s content is :

  module FFmpeg [system][extern_c] {
  
  
  
      header "include/libavcodec/avcodec.h"
  
      header "include/libavdevice/avdevice.h"
  
      header "include/libavfilter/avfilter.h"
  
      header "include/libavformat/avformat.h"
  
      header "include/libavutil/avutil.h"
  
      header "include/libswresample/swresample.h"
  
      header "include/libswscale/swscale.h"
  
  
  
      export *
  
  }

  Project tree is :

  

  5. Set Import paths for both project settings and target settings to
     $(SRCROOT)/MediaToolkit/Libraries/FFmpeg/**
  6. My source code is :

  import Foundation
  
  import FFmpeg
  
  
  
  public class MediaToolkit {
  
      public init(){}
  
  
  
      public func hello() {
  
          print("AVFMT_NOFILE: \(AVFMT_NOFILE)")
  
          avformat_network_init()
  
      }
  
  }

  When I build it, I received error

  Undefined symbols for architecture arm64:
  
    "_avformat_network_init", referenced from:
  
        MediaToolkit.MediaToolkit.hello(Swift.String) -> () in MediaToolkit.o
  
  ld: symbol(s) not found for architecture arm64
  
  clang: error: linker command failed with exit code 1 (use -v to see invocation)

  If I remove line avformat_network_init(), it will print AVFMT_NOFILE: 1

• Using ffmpeg static libraries in an visual studio explress C++ 2010 project

  29 octobre 2015, par Yvo Götz

  As the title says, I have been trying to get ffmpeg/libav libraries to work in MSVC++ 2010.
  However, I keep running in the following error while coding on debug mode.

  code :

  extern "C" 
  
  {
  
      #ifndef __STDC_CONSTANT_MACROS
  
      #define __STDC_CONSTANT_MACROS
  
      #endif
  
      #include 
  
      #include 
  
      #include 
  
      #include 
  
  }
  
  int main( int argc, char* argv[] ) 
  
  {
  
      av_register_all();
  
      return 0;
  
  }

  console :

  1>------ Build started: Project: ffmpeg, Configuration: Debug Win32 ------
  
  1>ffmpeg.obj : error LNK2019: unresolved external symbol _av_register_all referenced in       function _main
  
  1>C:\Users\okki\documents\visual studio 2010\Projects\ffmpeg\Debug\ffmpeg.exe : fatal    error LNK1120: 1 unresolved externals
  
  ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

  I used zeranoe’s latest build git-56ba331 (2013-05-14).

  And I have tried the following to fix this :

  • configuring the project to look for both the x64 and x86 libraries.
  • Add the DLLs from the ’shared’ package to both library folders.
  • Add the library directory to both the linker options and VC++ Directories.

  I have been stuck on this for a while, and any suggestion can help.
  If any extra info is needed I will happily provide.