Recherche avancée

Médias (5)

Mot : - Tags -/open film making

Autres articles (58)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

Sur d’autres sites (7310)

  • Unable to link FFMpeg libraries in Visual studio 2012

    29 juin 2013, par Pferd

    I have been trying to link the FFMPEG static libraries to Visual studio 2012 in c++ environment. But i get the following error.

    • Error 1 error LNK1104 : cannot open file
      'avcodec.lib' C :\Users\username\Documents\Visual Studio
      2012\Projects\ConsoleApplication5\ConsoleApplication5\LINK ConsoleApplication5

    my lib files were located in C :\Users\username\Documents\Visual Studio 2012\Projects\ConsoleApplication5\ConsoleApplication5\ExtLib\lib

    The compile seems to be fine. The command line is

    • /Yu"stdafx.h" /GS /W3 /Zc:wchar_t
      /I"C :\Users\username\Documents\Visual Studio
      2012\Projects\ConsoleApplication5\ConsoleApplication5\ExtLib\include"
      /Zi /Gm /Od /sdl /Fd"x64\Debug\vc110.pdb" /fp:precise /D "WIN32" /D
      "_DEBUG" /D "_CONSOLE" /D "_UNICODE" /D "UNICODE" /errorReport:prompt
      /WX- /Zc:forScope /RTC1 /Gd /MTd /Fa"x64\Debug\" /EHsc /nologo
      /Fo"x64\Debug\" /Fp"x64\Debug\ConsoleApplication5.pch"

    The main issue seems to be at the linking stage where I have just not been able to get VS2012 to find my ffmpeg .lib files

    The linker command line is below :

    • /OUT :"C :\Users\username\Documents\Visual Studio
      2012\Projects\ConsoleApplication5\x64\Debug\ConsoleApplication5.exe"
      /MANIFEST /NXCOMPAT /PDB :"C :\Users\username\Documents\Visual Studio
      2012\Projects\ConsoleApplication5\x64\Debug\ConsoleApplication5.pdb"
      /DYNAMICBASE "avcodec.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 /MACHINE:X64 /OPT:NOREF /INCREMENTAL
      /PGD :"C :\Users\username\Documents\Visual Studio
      2012\Projects\ConsoleApplication5\x64\Debug\ConsoleApplication5.pgd"
      /SUBSYSTEM:CONSOLE /MANIFESTUAC :"level='asInvoker' uiAccess='false'"
      /ManifestFile :"x64\Debug\ConsoleApplication5.exe.intermediate.manifest"
      /ERRORREPORT:PROMPT /NOLOGO
      /LIBPATH :"/LIBPATH:C :\Users\username\Documents\Visual Studio
      2012\Projects\ConsoleApplication5\ConsoleApplication5\ExtLib\lib"
      /TLBID:1

    I cant figure out why the linker cant locate my ffmpeg lib files even though they are physically located in the /LIBPATH area - c :...\vs12...\ExtLib\lib

  • FFmpeg : Build ffplay on Windows with Visual Studio and MSYS2

    13 septembre 2023, par San Zhang

    I have built FFmpeg on Windows with Visual Studio and MSYS2.

    


    My problem is, ffplay.exe is not built. Some search online suggests the reason might be of missing dependencies(most likely sdl2). I then installed sdl2 with MSYS2, and realized that the only sdl2 package available was built with MinGW. I imagine this means Visual Studio won't be able to use it to build ffplay.exe.

    


    My question : I can download sdl2 that's built with VC++, but how do I incorporate that into the FFmpeg build ? Do I simply put SDL2.dll under [MSYS2_Folder]\mingw64\bin ?

    


    Any thought/idea ?

    


  • Revision 65f13afd7d : Fix building for arm with Visual Studio 2013 The microsoft build tools explicit

    4 mai 2014, par Martin Storsjo

    Changed Paths :
     Modify /build/make/configure.sh


     Modify /build/make/gen_msvs_vcxproj.sh



    Fix building for arm with Visual Studio 2013

    The microsoft build tools explicitly disallow building for arm in
    the "desktop" target configuration ; one has to target "Windows
    Store" apps (aka WinRT/Metro) or Windows Phone. In Visual Studio
    2012, one could just pick the v110_wp80 toolset which made the
    vcxproj files buildable. In Visual Studio 2013, picking the v120_wp81
    toolset isn’t enough - one has to configure the vcxproj files
    as an "AppContainerApplication". This has the implication that
    you can’t just build a plain .exe (such as the examples) - an .exe
    project would need to have an AppxManifest file. Therefore we can
    only build the library itself.

    If loaded into Visual Studio for Windows (the Windows Store/Phone
    version of Visual Studio, not the Desktop one), the obj_int_extract
    project is omitted since it’s treated as incompatible. Building
    from the command line with msbuild works fine though.

    The armv7-win32-vs12 target was added as part of a638bdf4 even
    though actual use of it hadn’t been tested.

    Change-Id : Iee8088252cf790317aeb6b417d29058225f1f629

Navigation