Recherche avancée

Sur d’autres sites (11225)

• Evolution #2050 : site vide au début

  10 mai 2011, par cedric -

  voir aussi #2056

• Libavcodec "the procedure entry point for av_frame_alloc could not be located" error in Visual Studio 2017 C++ project

  25 novembre 2019, par Aves

  I am trying to use libavcodec from ffmpeg library in C++ with Visual Studio 2017 Community. I downloaded the latest x64 dev and shared builds from zeranoe (version 20171217), set up include directories and additional libraries in Visual Studio for x64 build, added DLL files from shared package to my PATH.

  This is my sample test code :

  extern "C" {
  
  #include 
  
  }
  
  int main() {
  
      avcodec_register_all();
  
      AVFrame *pAvFrame = av_frame_alloc();
  
      av_frame_free(&pAvFrame);
  
      return 0;
  
  }

  The code compiles without problems but when I run the application I see a dialogue window with error message "the procedure entry point for av_frame_alloc could not be located in DLL" (actual message is not in English, this is the translated version).

  I tried to set Linker->Optimization->References to /OPT:NOREF as it was advised in the similar questions but it did not help.

  Dependency walker shows that av_frame_alloc is exported, "Entry Point" is not bound. A little bit strange is that av_frame_alloc is displayed in both avcodec-58.dll (as red) and avutil-56.dll (as green). Maybe the reason is that the application is trying to get this function from avcodec instead of avutil, but I’m not sure, since I did not check the source code of these libraries.

  So the question is how to set up such a simple FFMPEG-based C++ project in VS2017, where I’m wrong ?

  UPD. 1.

  Linker flags : /OUT :"C :\work\code\TestFfmpeg\x64\Release\TestFfmpeg.exe" /MANIFEST /NXCOMPAT /PDB :"C :\work\code\TestFfmpeg\x64\Release\TestFfmpeg.pdb" /DYNAMICBASE "c :\work\dev\ffmpeg-20171217-387ee1d-win64-dev\lib*.lib" "kernel32.lib" "user32.lib" "gdi32.lib" "winspool.lib" "comdlg32.lib" "advapi32.lib" "shell32.lib" "ole32.lib" "oleaut32.lib" "uuid.lib" "odbc32.lib" "odbccp32.lib" /DEBUG:FULL /MACHINE:X64 /OPT:NOREF /PGD :"C :\work\code\TestFfmpeg\x64\Release\TestFfmpeg.pgd" /MANIFESTUAC :"level=’asInvoker’ uiAccess=’false’" /ManifestFile :"x64\Release\TestFfmpeg.exe.intermediate.manifest" /OPT:ICF /ERRORREPORT:PROMPT /NOLOGO /TLBID:1

• Documentation #3972 : template variants and possible bug ?

  6 juillet 2017, par Kamran Mir Hazar

  I have SPIP 3.1.6 [23444].

  On Thu, Jul 6, 2017 at 8:20 PM, <redmine@spip.org> wrote :

  La demande #3972 a été mise à jour par nico d_.

  Hi,
  which version of SPIP are you using ?

  ---

  Anomalie #3972 : template variants and possible bug ?

  Auteur : Kamran Mir Hazar
  Statut : Nouveau
  Priorité : Normal
  Assigné à :
  Catégorie :
  Version cible :
  Resolution :
  Navigateur :

  Hello,
  The following template variants do not work for me :
  I have section number 101, with articles in fa and en languages in it.
  I have also files article.html for the main site’s language which is fa, and
  article.en.html for the en language articles. Both work fine in general. I
  created two other variants to apply articles in section 101 with two
  separate languages. They are : article=101.fa.html and article=101.en.html .
  SPIP ignores these two variants and proceeds article.html for fa language
  articles, and article.en.html for en language articles in section 101, like
  the other sections. I added also article=101.html to see if it works, but
  didn’t.
  I asked this in French and English mailing lists, but couldn’t find any
  solution.
  Thank you
  Kamran

  PS : I tried based of the following article :
  https://www.spip.net/en_article4363.html

  ---

  Vous recevez ce mail car vous êtes impliqués sur ce projet.
  Pour changer les préférences d’envoi de mail, allez sur
  http://core.spip.org/my/account