Recherche avancée

Médias (0)

Mot : - Tags -/flash

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (18)

  • La file d’attente de SPIPmotion

    28 novembre 2010, par

    Une file d’attente stockée dans la base de donnée
    Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
    Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...)

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

  • 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 (3121)

  • FFMPEG android compile error

    11 octobre 2017, par Sujith Manjavana

    I’m trying to compile ffmpeg for android using ndk. os:ubuntu 13.10. I followed this tutorial. but when i run the build_android.sh it gives me the following errors-

    sujith@Vaio:~$ cd /home/sujith/ndk9d/sources/ffmpeg
    sujith@Vaio:~/ndk9d/sources/ffmpeg$ sudo chmod +x build_android.sh
    [sudo] password for sujith:
    sujith@Vaio:~/ndk9d/sources/ffmpeg$ ./build_android.sh
    /home/sujith/sujith/ndk9d/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-         x86_64/bin/arm-linux-androideabi-gcc is unable to create an executable file.
    C compiler test failed.

    If you think configure made a mistake, make sure you are using the latest
    version from Git.  If the latest version fails, report the problem to the
    ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net.
    Include the log file "config.log" produced by configure as this will help
    solving the problem.
    Makefile:2: config.mak: No such file or directory
    Makefile:53: /common.mak: No such file or directory
    Makefile:93: /libavutil/Makefile: No such file or directory
    Makefile:93: /library.mak: No such file or directory
    Makefile:95: /doc/Makefile: No such file or directory
    Makefile:178: /tests/Makefile: No such file or directory
    make: *** No rule to make target `/tests/Makefile'.  Stop.
    Makefile:2: config.mak: No such file or directory
    Makefile:53: /common.mak: No such file or directory
    Makefile:93: /libavutil/Makefile: No such file or directory
    Makefile:93: /library.mak: No such file or directory
    Makefile:95: /doc/Makefile: No such file or directory
    Makefile:178: /tests/Makefile: No such file or directory
    make: *** No rule to make target `/tests/Makefile'.  Stop.
    Makefile:2: config.mak: No such file or directory
    Makefile:53: /common.mak: No such file or directory
    Makefile:93: /libavutil/Makefile: No such file or directory
    Makefile:93: /library.mak: No such file or directory
    Makefile:95: /doc/Makefile: No such file or directory
    Makefile:178: /tests/Makefile: No such file or directory
    make: *** No rule to make target `/tests/Makefile'.  Stop.

    here is my build_android.sh

    #!/bin/bash
    NDK=$HOME/sujith/ndk9d
    SYSROOT=$NDK/platforms/android-9/arch-arm/
    TOOLCHAIN=$NDK/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86_64
    function build_one
    {
    ./configure \
    --prefix=$PREFIX \
    --enable-shared \
    --disable-static \
    --disable-doc \
    --disable-ffmpeg \
    --disable-ffplay \
    --disable-ffprobe \
    --disable-ffserver \
    --disable-avdevice \
    --disable-doc \
    --disable-symver \
    --cross-prefix=$TOOLCHAIN/bin/arm-linux-androideabi- \
    --target-os=linux \
    --arch=arm \
    --enable-cross-compile \
    --sysroot=$SYSROOT \
    --extra-cflags="-Os -fpic $ADDI_CFLAGS" \
    --extra-ldflags="$ADDI_LDFLAGS" \
    $ADDITIONAL_CONFIGURE_FLAG
    make clean
    make
    make install
    }
    CPU=arm
    PREFIX=$(pwd)/android/$CPU
    ADDI_CFLAGS="-marm"
    build_one

    my build_android.sh is located in ffmpeg source root directory.
    how to fix this ? please help me..

  • configure : Make require_cc() and require_cpp_condition() functions consistent

    28 mars 2018, par Diego Biurrun
    configure : Make require_cc() and require_cpp_condition() functions consistent
    

    Their API and implementation is different from other require_foo() functions,
    which violates the rule of least astonishment.

    • [DBH] configure
  • FFmpeg : building example C codes

    23 février 2021, par J. S.

    I have configured and compiled the FFmpeg library using this link :
https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu

    



    Now, I am trying to build example C codes provided by FFmpeg from here :
https://github.com/FFmpeg/FFmpeg/tree/master/doc/examples

    



    However, when I run make install-examples or make install (suggested by /example/README), I receive this kind of message :

    



    


    make : *** No rule to make target '/doc/examples/README', needed by
 'install-examples'. Stop.

    


    



    I thought this may be due to the rules not being in the correct MakeFile format (I am not sure why they refers to README). How should I go about in fixing this and compiling the example codes ? I have tried to find solutions about this, but there doesn't seem to be much information online.

    



    Thank you.