Recherche avancée

Sur d’autres sites (5296)

• Building FFmpeg.NET .dll

  9 juin 2014, par user2656632

  I need to use some FFmpeg functions in C# (to be precise, in GTK#). So I downloaded wrapper FFmpeg.NET. After that I try to build FFmpeg.NET.2008.sln(reference : I will build dll in Visual Studio 2008, but will use in GTK#), then get the following errors :

  Error 1 error PRJ0019 : A tool returned an error code from "Performing
  Makefile project actions" FFMpeg.NET
  Error 2 The referenced assembly
  "C :\Users\Zhenya\Documents\ffmpegdotnet-94877\bin
  (debug shared)\ffmpeg.net.dll" was not found. If this assembly is
  produced by another one of your projects, please make sure to build
  that project before building this one.

  How to fix these issues ?
  Or how to correctly build this wrapper to get .dll ?

• Preventing the python and ffmpeg heroku buildpacks from overwriting LD_LIBRARY_PATH

  3 mars 2014, par Simon

  I'm deployng a Django app to heroku, which requires ffmpeg. To accomplish this I am using heroku-buildpack-multi to install both heroku-buildpack-ffmpeg and heroku-buildpack-python, and all of that works fine. The problem is my that app also depends on django-pylibmc-sasl, python-memcached, pylibmc et al. which, as per usual, heroku senses and automatically installs libmemcached for me.

  Here's where something goes a little wrong. If I remove the custom buildpack everything runs fine (except for ffmpeg obviously). As soon as I add it in, however, while I can run ffmpeg, python fails on import pylibmc (or rather on import _pylibmc inside the module itself). After a amount of head-scratching I decided to have a look at the environment variables, here's what I got :

  With only the Python buildpack enabled :

  LD_LIBRARY_PATH=/app/.heroku/vendor/lib

  With both the Python and the ffmpeg buildpacks enabled :

  LD_LIBRARY_PATH=:vendor/ffmpeg/lib

  It looks like one or both of the buildpacks simply overwrites the other, or avoids setting the variable should it be already set. The ffmpeg buildpack seems to set LD_LIBRARY_PATH in a way that looks kosher to me, while the Python buildpack does a few things that I don't really understand the reason for.

  Solution

  Anyway, after manually overriding the library path using heroku config:set LD_LIBRARY_PATH=/app/.heroku/vendor/lib:vendor/ffmpeg/lib I am able to use both libmemcached and ffmpeg, but it doesn't feel too robust. What if something changes in one of the buildpacks path settings, or I add another buildpack - then I would have to manually edit the library path variable.

  Better solution ?

  So, while this is not really an urgent question at all, I simply would like to know :

  • Is there a better way of solving this issue ?
  • Might I have made some configuration error leading up to the path conflict ?
  • Should this be considered a bug in either of the buildpacks ?

• How to build FFmpeg.NET .dll ?

  1er mars 2014, par user2656632

  I need to use some FFmpeg functions in C# (to be precise, in GTK#). So I downloaded wrapper FFmpeg.NET. After that I try to build FFMpeg.NET.2008.sln(reference : I will build dll in Visual Studio 2008, but will use in GTK#), then get the following errors :

  Error 1 error PRJ0019 : A tool returned an error code from "Performing
  Makefile project actions" FFMpeg.NET
  Error 2 The referenced assembly
  "C :\Users\Zhenya\Documents\ffmpegdotnet-94877(CLEAR)\bin
  (debug shared)\ffmpeg.net.dll" was not found. If this assembly is
  produced by another one of your projects, please make sure to build
  that project before building this one.

  How to fix these issues ?

  Or how to correctly build this wrapper to get .dll ?

  Thanks !