
Recherche avancée
Autres articles (105)
-
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 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 (...) -
Multilang : améliorer l’interface pour les blocs multilingues
18 février 2011, parMultilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela. -
Personnaliser en ajoutant son logo, sa bannière ou son image de fond
5 septembre 2013, parCertains 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 ;
Sur d’autres sites (18427)
-
avio : Add avio_read wrapper to simplify error checking
26 mai 2015, par Vittorio Giovara -
ffmpeg-python - checking if file is video
14 avril 2021, par Gwen JHow do I go about identifying if the file is an actual video media file ?
While doing a probe, it returns a 'codec_type' : 'video' even for a text file.


vid_info = ffmpeg.probe(f'{filepath}/test.txt')['streams'];



-
Configuring install path : prefix=[PREFIX] not fully understood
29 septembre 2019, par whatshisfaceI think this is simply a general c++ question :
I’m attempting to compile a local version of ffmpeg on Linux Fedora using the gnu c++ compiler. I have source code in a bunch of folders under :
~/<username>/Downloads/Code/ffmpeg_sources/
</username>which is where I’m attempting to set the config flags to install the build to a target not under this tree but at a root level directory with local shared libraries :
/usr/local/
There is this following section near the beginning of the configuration file :
Standard options:
--prefix=PREFIX install in PREFIX []
--bindir=DIR install binaries in DIR [PREFIX/bin]
--datadir=DIR install data files in DIR [PREFIX/share/ffmpeg]
--docdir=DIR install documentation in DIR [PREFIX/share/doc/ffmpeg]
--libdir=DIR install libs in DIR [PREFIX/lib]
--shlibdir=DIR install shared libs in DIR [PREFIX/lib]
--incdir=DIR install includes in DIR [PREFIX/include]
--mandir=DIR install man page in DIR [PREFIX/share/man]
--enable-rpath use rpath to allow installing libraries in paths
not part of the dynamic linker search pathI may have completely misunderstood this, but I thought that setting a value like
--prefix=/usr/local
or
--prefix=[/usr/local]
might work, but it appears not to, as once the ./config, make&&make install is complete, it has done a bunch of stuff but there’s nothing installed at the target. There are a LOT of new executable files built in the source directory, so presumably the build is working but I’m simply specifying the paths incorrectly ? A part of the same problem is that it’s unclear whether, once I’ve set the
--prefix=[PREFIX]
correctly, I need to set all of the further
--datadir, --libdir
etc. or whether the first —prefix value is enough ?
What is the above configuration syntax trying to show me ?