Recherche avancée

Médias (1)

Mot : - Tags -/3GS

Autres articles (97)

  • 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.

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Que fait exactement ce script ?

    18 janvier 2011, par

    Ce script est écrit en bash. Il est donc facilement utilisable sur n’importe quel serveur.
    Il n’est compatible qu’avec une liste de distributions précises (voir Liste des distributions compatibles).
    Installation de dépendances de MediaSPIP
    Son rôle principal est d’installer l’ensemble des dépendances logicielles nécessaires coté serveur à savoir :
    Les outils de base pour pouvoir installer le reste des dépendances Les outils de développements : build-essential (via APT depuis les dépôts officiels) ; (...)

Sur d’autres sites (4313)

  • Merge commit ’582d4211e00015b68626f77ce4af53161e2b1713’

    14 novembre 2016, par Hendrik Leppkes
    Merge commit ’582d4211e00015b68626f77ce4af53161e2b1713’

    * commit ’582d4211e00015b68626f77ce4af53161e2b1713’ :
    
  vf_scale_vaapi : Respect driver quirks around buffer destruction
    

    Merged-by : Hendrik Leppkes <h.leppkes@gmail.com>

  • Merge commit ’221ffca6314ed3ba9d38464ea50cd85251c04e74’

    14 novembre 2016, par Hendrik Leppkes
    Merge commit ’221ffca6314ed3ba9d38464ea50cd85251c04e74’

    * commit ’221ffca6314ed3ba9d38464ea50cd85251c04e74’ :
    
  vaapi_encode : Respect driver quirks around buffer destruction
    

    Merged-by : Hendrik Leppkes <h.leppkes@gmail.com>

  • 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

Navigation