Recherche avancée

Médias (1)

Mot : - Tags -/berlin

Autres articles (94)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Gestion des droits de création et d’édition des objets

    8 février 2011, par

    Par défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;

Sur d’autres sites (10631)

  • Unresolved externals with statically built ffmpeg on Windows

    7 juillet 2013, par user1764961

    I built ffmpeg 1.2.1 as a static lib - x64, debug. And I tried to open one of my older projects that links against it. After modifying some changed APIs and similar in my source, it compiled fine, but I have major problems with linking.

    EDITED : the complete latest build output :

    1>libavformat.a(mov.o) : error LNK2019: unresolved external symbol __imp__gmtime64 referenced in function mov_read_mvhd
    1>libavutil.a(parseutils.o) : error LNK2001: unresolved external symbol __imp__gmtime64
    1>libavformat.a(os_support.o) : error LNK2019: unresolved external symbol __imp__wsopen referenced in function ff_win32_open
    1>libavcodec.a(pthread.o) : error LNK2019: unresolved external symbol __imp__beginthreadex referenced in function ff_thread_init
    1>libavcodec.a(frame_thread_encoder.o) : error LNK2001: unresolved external symbol __imp__beginthreadex
    1>libavutil.a(parseutils.o) : error LNK2019: unresolved external symbol __imp__localtime64 referenced in function av_parse_time
    1>libavutil.a(parseutils.o) : error LNK2019: unresolved external symbol __imp__time64 referenced in function av_parse_time
    1>libavutil.a(parseutils.o) : error LNK2019: unresolved external symbol __imp__mktime64 referenced in function av_parse_time
    1>libmingwex.a(lib64_libmingwex_a-mingw_output_format.o) : error LNK2019: unresolved external symbol __mingw_get_msvcrt_handle referenced in function __mingw_set_output_format
    1>libmingwex.a(lib64_libmingwex_a-mingw_get_codepage.o) : error LNK2001: unresolved external symbol __mingw_get_msvcrt_handle

    What am I doing wrong ?
    What am I missing here ?
    Does ffmpeg even work today on Windows platform as a static lib, or it becomes less functional on Windows with each new version ?

  • How to compile ffmpeg-1.2.1 on windows with cygwin and android ndk r8e

    17 juin 2013, par Pratik

    I have been trying to find the solution from last few days but unfortunately not even found a single solution which provides me the right direction..! I have goggled no of posts,examples etc.Lots of developers are facing the same problem.I know these things are easy to compile on OS X or any Linux.

    so my question is that :

    How to compile ffmpeg-1.2.1 on windows with cygwin and android ndk r8e
    or
    if anybody had successfully complied the previous releases of ff-mpeg on windows they can tell me the necessary steps.

    I am using windows-7(32-bit)

    Downloaded sources :

    1) I have downloaded latest FFmpeg 1.2.1 "Magic" from FFMPEG sources.

    2) I have downloaded all the necessary packages in cygwin.

    3) I have also downloaded android-ndk-r8e from Android dev site.

    I am trying to find the solution but
    any help would be appriciated.

  • configure : Don’t explicitly disable PIC for windows targets

    28 mai 2013, par Martin Storsjö
    configure : Don’t explicitly disable PIC for windows targets
    

    This reverts e08c946c6 and 05165c2f7a. The actual intention of
    e08c946c6 was to fix shared library builds for arm/win32, which
    can also be accomplished in other ways.

    Disabling pic on those platforms broke inline assembly on cygwin/64
    (since some inline assembly requires knowing whether we are building
    as PIC or not), and might also break inline assembly on other
    compilers on windows.

    As a side-effect, this unfortunately brings back all the warnings
    about PIC not having any effect on that platform.

    Signed-off-by : Martin Storsjö <martin@martin.st>

    • [DH] configure