Recherche avancée

Médias (1)

Mot : - Tags -/belgique

Autres articles (106)

  • 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" (...)

  • Le profil des utilisateurs

    12 avril 2011, par

    Chaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
    L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...)

  • Submit enhancements and plugins

    13 avril 2011

    If you have developed a new extension to add one or more useful features to MediaSPIP, let us know and its integration into the core MedisSPIP functionality will be considered.
    You can use the development discussion list to request for help with creating a plugin. As MediaSPIP is based on SPIP - or you can use the SPIP discussion list SPIP-Zone.

Sur d’autres sites (10469)

  • configure : use proper Windows-style static library naming

    3 août, par Kacper Michajłow
    configure : use proper Windows-style static library naming

    On Windows, static libraries are typically named with a .lib extension.
    
An exception to this is MinGW targets, which are treated as a distinct
    
target-os.
    

    Using Windows-style naming allows `clang` to be used as the linker
    
driver, instead of invoking link or lld-link directly. The latter
    
approach requires manually specifying standard libraries when compiling
    
with `clang` rather than `clang-cl`, and manually specifying standard
    
libraries may be error-prone or incomplete.
    

    Using Windows-style naming allows Clang to be used as the linker driver,
    
instead of invoking link or lld-link directly. The latter approach
    
requires manually specifying standard libraries, which may be
    
error-prone or incomplete.
    

    This change also improves support for LTO and sanitizer builds, where
    
it's significantly easier to let the compiler driver manage the
    
necessary linker flags.
    

    It fixes issues where Clang is asked to link `-lavcodec`, which gets
    
passed to the linker as avcodec.lib, resulting in an error like :
    
lld-link : error : could not open 'avcodec.lib' : no such file or directory
    
This happens because `libavcodec.a` was unexpectedly generated, not
    
`avcodec.lib` expected by tooling.
    

    Additionally, using `clang` (not `clang-cl`) is simplified, as it does
    
not use autolinking like MSVC/clang-cl does. Now `—ld=clang` can be
    
used to add all the required libraries. Previously, building with
    
`clang` was only possible by using `—ld=lld-link` and manually
    
specifying system dependencies in `extra-ldflags`.
    

    Note that those changes doesn't affect mingw build. MSVC builds will
    
produce .lib static libraries now, but the linking process itself is not
    
affected, because filenames are passed directly.
    

    To summarize in Windows non-mingw builds :
    
Static builds now produce `lib/avcodec.lib` instead of `lib/libavcodec.a`.
    
Shared builds remain unchanged, producing `bin/avcodec.lib` together with
    
`bin/avcodec-62.dll`.
    

    This also removes setting LD_LIB from Win32/64 target as there is one
    
type of .lib in practice. We cannot build both shared and static at the
    
same time as noted by the next line.
    

    Signed-off-by : Kacper Michajłow <kasper93@gmail.com>
    • [DH] configure

  • avformat/aacdec : strictly conform to K&R style

    18 mai 2024, par Marcus B Spencer
    avformat/aacdec : strictly conform to K&R style

    In the K&R style, a single-statement block does not have braces.
    
Edit the code to conform to this rule.
    

    It is FFmpeg's code formatting convention to use K&R style.
    

    Signed-off-by : Marcus B Spencer <marcus@marcusspencer.xyz>
    • [DH] libavformat/aacdec.c

  • lavf/movenc : small cleanup for style

    21 mars 2024, par Jun Zhao
    lavf/movenc : small cleanup for style

    Small cleanup for style, indent, switch case lables.
    
BTW, the preferred way to ease multiple indentation levels in a
    
switch statement is to align the switch and its subordinate
    
case labels in the same column
    

    Signed-off-by : Jun Zhao <barryjzhao@tencent.com>
    • [DH] libavformat/movenc.c

Navigation