Recherche avancée

Médias (3)

Mot : - Tags -/pdf

Autres articles (44)

  • Modifier la date de publication

    21 juin 2013, par

    Comment changer la date de publication d’un média ?
    Il faut au préalable rajouter un champ "Date de publication" dans le masque de formulaire adéquat :
    Administrer > Configuration des masques de formulaires > Sélectionner "Un média"
    Dans la rubrique "Champs à ajouter, cocher "Date de publication "
    Cliquer en bas de la page sur Enregistrer

  • Pas question de marché, de cloud etc...

    10 avril 2011

    Le vocabulaire utilisé sur ce site essaie d’éviter toute référence à la mode qui fleurit allègrement
    sur le web 2.0 et dans les entreprises qui en vivent.
    Vous êtes donc invité à bannir l’utilisation des termes "Brand", "Cloud", "Marché" etc...
    Notre motivation est avant tout de créer un outil simple, accessible à pour tout le monde, favorisant
    le partage de créations sur Internet et permettant aux auteurs de garder une autonomie optimale.
    Aucun "contrat Gold ou Premium" n’est donc prévu, aucun (...)

  • Activation de l’inscription des visiteurs

    12 avril 2011, par

    Il est également possible d’activer l’inscription des visiteurs ce qui permettra à tout un chacun d’ouvrir soit même un compte sur le canal en question dans le cadre de projets ouverts par exemple.
    Pour ce faire, il suffit d’aller dans l’espace de configuration du site en choisissant le sous menus "Gestion des utilisateurs". Le premier formulaire visible correspond à cette fonctionnalité.
    Par défaut, MediaSPIP a créé lors de son initialisation un élément de menu dans le menu du haut de la page menant (...)

Sur d’autres sites (6694)

  • doc : fix generating doxy with out-of-tree builds

    24 avril 2021, par Anton Khirnov
    doc : fix generating doxy with out-of-tree builds
    

    Broken in 753930bc7300dd595c4bab51c5a70d1da9083da4, as the path to
    Doxyfile passed to doxy-wrapper.sh is relative to the build dir, while
    the recipe cd's to the source dir before invoking the wrapper.

    • [DH] doc/Makefile
    • [DH] doc/doxy-wrapper.sh
  • FFmpeg 0.6 fails to build on ubuntu 16.04

    18 août 2016, par Andreas Geo

    I am trying to build ffmpeg 0.6 for a project I have. I am using Ubuntu 16.04 and when I try to build it I get the following error :

    In file included from libavcodec/mpegvideo.h:32:0,
                 from libavcodec/vaapi_internal.h:30,
                 from libavcodec/vaapi_mpeg4.c:23:
    libavcodec/get_bits.h: In function ‘skip_bits’:
    libavcodec/get_bits.h:387:17: warning: variable ‘re_cache’ set but not used [-Wunused-but-set-variable]
          OPEN_READER(re, s)
                      ^
    libavcodec/get_bits.h:135:13: note: in definition of macro ‘OPEN_READER’
        int name##_cache= 0;\
            ^
    libavcodec/vaapi_mpeg4.c: In function ‘vaapi_mpeg4_start_frame’:
    libavcodec/vaapi_mpeg4.c:89:73: error: implicit declaration of function ‘ff_h263_get_gob_height’ [-Werror=implicit-function-declaration]
    pic_param->num_macroblocks_in_gob           = s->mb_width * ff_h263_get
                                                               ^
    cc1: some warnings being treated as errors
    common.mak:40: recipe for target 'libavcodec/vaapi_mpeg4.o' failed
    make: *** [libavcodec/vaapi_mpeg4.o] Error 1

    I faced a similar error with ffserver.o file but i downloaded these files here and it fixed it :

    sudo apt-get -y install autoconf automake build-essential libass-dev libfreetype6-dev \
    libsdl1.2-dev libtheora-dev libtool libva-dev libvdpau-dev libvorbis-dev libxcb1-dev libxcb-shm0-dev \
    libxcb-xfixes0-dev pkg-config texinfo zlib1g-dev

    I believe its something similar. Anybody has any ideas ??
    Thank you.

  • How to import .pc from a pkgconfig folder using cmake ?

    20 août 2019, par Sailanarmo

    I am currently building FFmpeg as an external project. FFmpeg builds correctly and the library is stuck inside an appropriate lib folder. And inside that lib folder a pkgconfig folder is placed inside with all of the .pc files with the information of all of the associated libraries. Of course, I could be thinking about this wrong. However when I built FFmpeg, I had to use a pkg_congig so it could link with the libraries of x264. Here is my ffmpeg_exteral.cmake file :

    SET_PROPERTY(DIRECTORY PROPERTY "EP_BASE" ${ep_base})

    set( FFmpeg_url "https://github.com/FFmpeg/FFmpeg.git")
    set( FFmpeg_TAG "n4.2")
    set(FFmpeg_depends "x264_external_download")

    set(PATH_DEPENDS "${x264_LIBRARY_DIR}/pkgconfig")

    ExternalProject_Add(FFmpeg_external_download
     DEPENDS ${FFmpeg_depends}
     GIT_REPOSITORY ${FFmpeg_url}
     GIT_TAG ${FFmpeg_TAG}
     UPDATE_COMMAND ""
     PATCH_COMMAND ""
     INSTALL_COMMAND ""
     INSTALL_DIR ""
     CONFIGURE_COMMAND PKG_CONFIG_PATH=${PATH_DEPENDS} /configure
       --prefix=/build
       --enable-static
       --extra-cflags=-I${x264_INCLUDE_DIR}\ --static
       --extra-ldflags=-L${x264_LIBRARY_DIR}
       --enable-gpl
       --enable-libx264
     BUILD_COMMAND make
       -j8
    )

    #CACHE PATH "" seems to write the path to a file that I can set
    #library paths to.

    ExternalProject_Get_Property(FFmpeg_external_download BINARY_DIR)

    set(FFmpeg_LIBRARY_DIR ${BINARY_DIR}/build/lib CACHE INTERNAL "")
    set(FFmpeg_INCLUDE_DIR ${BINARY_DIR}/build/include CACHE INTERNAL "")

    add_library(FFmpeg_external STATIC IMPORTED)

    And this links directly with a x264_external.cmake

    SET_PROPERTY(DIRECTORY PROPERTY "EP_BASE" ${ep_base})

    set( x264_url "https://code.videolan.org/videolan/x264.git")
    set( x264_TAG "origin/stable")


    ##[[
     The configure command is required because FFMPEG will try to build these
     libraries when x264 static does not need them.
    ]]
    ExternalProject_Add(x264_external_download
     GIT_REPOSITORY ${x264_url}
     GIT_TAG ${x264_TAG}
     UPDATE_COMMAND ""
     PATCH_COMMAND ""
     INSTALL_COMMAND ""
     INSTALL_DIR ""
     CONFIGURE_COMMAND /configure
       --prefix=/x264_build
       --enable-static
       --disable-opencl
       --disable-avs
       --disable-cli
       --disable-ffms
       --disable-gpac
       --disable-lavf
       --disable-swscale
     BUILD_COMMAND make install
       -j8
    )

    #CACHE PATH "" seems to write the path to a file that I can set
    #library paths to.

    ExternalProject_Get_Property(x264_external_download BINARY_DIR)

    set(x264_LIBRARY_DIR ${BINARY_DIR}/x264_build/lib CACHE INTERNAL "")
    set(x264_BINARY_DIR ${BINARY_DIR}/x264_build/bin CACHE INTERNAL "")
    set(x264_INCLUDE_DIR ${BINARY_DIR}/x264_build/include CACHE INTERNAL "")

    add_library(x264_external STATIC IMPORTED)

    As you can see, FFmpeg takes the pkg_config_path from the library directory of x264 and they link together just fine. However, now that I am trying to build a simple example to make sure FFmpeg is linking with my project. I get errors of undefined references to anything from FFmpeg. This is all main.cpp has :

    #include <iostream>
    #include <libavcodec></libavcodec>avcodec.h>
    #include <libavdevice></libavdevice>avdevice.h>
    #include <libavfilter></libavfilter>avfilter.h>
    #include <libavformat></libavformat>avformat.h>
    #include <libavformat></libavformat>avio.h>
    #include <libavutil></libavutil>avutil.h>

    int main()
    {
     std::cout &lt;&lt; "It compiled." &lt;&lt; std::endl;

     avformat_network_init();

     std::cout &lt;&lt; "It worked." &lt;&lt; std::endl;

     avformat_network_deinit();

    }
    </iostream>

    And in the cmake file that uses it, all it has is :

    set(CMAKE_PREFIX_PATH ${FFmpeg_LIBRARY_DIR}/pkgconfig)

    include_directories(${FFmpeg_INCLUDE_DIR})
    link_directories(${FFmpeg_LIBRARY_DIR})

    add_executable(Main main.cpp)

    add_dependencies(Main FFmpeg_external_download)

    I read that CMAKE_PREFIX_PATH will find and read in .pc files, however it doesn’t seem to be doing much here, and as far as I can tell, I am not really sure how to set PkgConfig to find a custom path for a package. And maybe this is linking correctly because I am doing this wrong. Any help on how to get these to link together would be tremendous help.

    EDIT : I forgot to say that FFmpeg builds 8 libraries that I am trying to link to in the lib folder. I have tried creating a library for each of them, setting their target properties to their libraries, and linking them to main using target_link_libraries and that hasn’t seemed to work either.

    EDIT 2 : Error message

    CMakeFiles/Main.dir/main.cpp.o: In function `main':
    main.cpp:(.text+0x2d): undefined reference to `avformat_network_init()'
    main.cpp:(.text+0x5a): undefined reference to `avformat_network_deinit()'
    collect2: error: ld returned 1 exit status
    Source/CMakeFiles/Main.dir/build.make:91: recipe for target 'bin/Main' failed
    make[2]: *** [bin/Main] Error 1
    CMakeFiles/Makefile2:242: recipe for target 'Source/CMakeFiles/Main.dir/all' failed
    make[1]: *** [Source/CMakeFiles/Main.dir/all] Error 2
    Makefile:83: recipe for target 'all' failed
    make: *** [all] Error 2

    EDIT 3 : Verbose output

    -L/home/sailanarmo/reeee/Superbuild/Build/FFmpeg_external_download/build/lib -Wl,-rpath,/home/sailanarmo/reeee/Superbuild/Build/FFmpeg_external_download/build/lib -lpthread ../Superbuild/Build/FFmpeg_external_download/build/lib/libavcodec.a ../Superbuild/Build/FFmpeg_external_download/build/lib/libavdevice.a ../Superbuild/Build/FFmpeg_external_download/build/lib/libavfilter.a ../Superbuild/Build/FFmpeg_external_download/build/lib/libavformat.a ../Superbuild/Build/FFmpeg_external_download/build/lib/libavutil.a ../Superbuild/Build/FFmpeg_external_download/build/lib/libpostproc.a ../Superbuild/Build/FFmpeg_external_download/build/lib/libswresample.a ../Superbuild/Build/FFmpeg_external_download/build/lib/libswscale.a