Recherche avancée

Sur d’autres sites (6643)

• src/flac/decode.c : Fix a cast-align warning from GCC.

  27 juin 2014, par Erik de Castro Lopo

  src/flac/decode.c : Fix a cast-align warning from GCC.
  The old code was creating an array of FLAC__int8, and then casting
  
  that to a set of signed and unsigned 16 and 32 bit integers. This
  
  was replaced with a single union containing all the requred array.
  This solution means that there are fewer pointer casts and actually
  
  gives the compiler more information with which to generate fast code.
  

  • [DH] src/flac/decode.c

• Merge commit ’165e9df19567ec0b6abee1ee2c26027e6d7aa7bf’

  25 juillet 2014, par Michael Niedermayer

  Merge commit ’165e9df19567ec0b6abee1ee2c26027e6d7aa7bf’
  * commit ’165e9df19567ec0b6abee1ee2c26027e6d7aa7bf’ :
  
    fft-test : Pass the right struct members instead of casting
  Merged-by : Michael Niedermayer <michaelni@gmx.at>
  

  • [DH] libavcodec/fft-test.c

• How would I dynamically link FFmpeg in a C# Project for use with FFMpegCore ?

  15 octobre 2024, par liamliam

  So far, I have FFMpegCore working in my project with a ffmpeg.exe dropped into the project directory. This works, but for LGPL license compliance FFmpeg requires dynamic linking :
  
Use dynamic linking (on windows, this means linking to dlls) for linking with FFmpeg libraries..

  


  While I understand the basic concept of dynamic vs static linking, my problem is likely a misunderstanding of how .dlls work and how they apply to C# and .NET.
  
Would it be possible to compile ffmpeg into a single .dll that could be accessed by FFMpegCore cross-platform ? From what I can gather in the source, FFMpegCore looks for an ffmpeg or ffmpeg.exe file in its configuration path.

  


  Is it possible to have .NET dynamically link FFmpeg and expose it to libraries for use or is that a complete misunderstanding and would I then need a wrapper library with different capabilities ?

  


  I've attempted to find the answer in the relevant documentation, but I found none for this specific use of either library. I suspect my problem might be a fundamental misunderstanding of how these tools work and work together.
My ideal result would be using FFMpegCore with an FFmpeg.dll that works cross-platform instead of the .exe.

  


  Edit 1 : @taratect's answer and graphic sent me down a path that cleared up quite a bit about exes and dlls. .Net compiles source code down to platform agnostic Intermediate Language in the form of a .dll or .exe(completely different to C++ variants of these files), which is executed by the Common Language Runtime using a Just In Time compiler to convert that Intermediate Language to Machine Code that can be run on the specific platform .Net is installed on. C++(FFmpeg) compiles directly to platform specific Machine Code (as shown in the graphic), confusingly in the form of a .dll or .exe (on Windows). .Net can indeed load and run machine code unmanaged by Common Language Runtime, since everything is run as Machine Code by the end, however memory and other complexities must then be managed by me, which seems to be what FFMpegCore does in wrapping the executable. I might still be confused/incorrect on some of this, unmanaged code is beyond my understanding so far.
This does more or less confirm that FFMpegCore probably can't be expected to use FFmpeg in the way I hoped and a better workaround might be having the user just supply an FFmpeg source or implement a downloader as part of installation so that I don't have to redistribute it at all.