
Recherche avancée
Autres articles (55)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
Creating farms of unique websites
13 avril 2011, parMediaSPIP 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" (...) -
Other interesting software
13 avril 2011, parWe don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
We don’t know them, we didn’t try them, but you can take a peek.
Videopress
Website : http://videopress.com/
License : GNU/GPL v2
Source code : (...)
Sur d’autres sites (8463)
-
Révision 18538 : Ca devrait être plus sympa de se connecter à SPIP depuis un smartphone ;)
17 septembre 2011, par tetue -Habillage des popup restées nues ; et des fenêtres en petite largeur, dont navigateurs mobiles, à l’aide de règles CSS media query
Bouton pour fermer la fenêtre
Et finalement, suppression des popup du formulaire de forum sur abonnement et de la page de login. Ce qui résoud (...)
-
Révision 18539 : Ca devrait être plus sympa de se connecter à SPIP depuis un smartphone ;)
17 septembre 2011, par tetue -Habillage des popup restées nues ; et des fenêtres en petite largeur, dont navigateurs mobiles, à l’aide de règles CSS media query
Bouton pour fermer la fenêtre
Et finalement, suppression des popup du formulaire de forum sur abonnement et de la page de login. Ce qui résoud (...)
-
How to compile ffmpeg for Windows statically with MSYS2 environment ?
17 janvier 2024, par usernameI want to build myself standalone statically linked ffmpeg binaries for Windows from official git source code with MSYS2 environment tools. But every time I get .exe file dynamically linked to mingw libraries that crashes with "The application was unable to start correctly (0xc000007b)" error even if I put required libbz2-1.dll, libiconv-2.dll and libwinpthread-1.dll libraries in it's folder.



I'm running MSYS2 environment with



msys2_shell.cmd -mingw64




line, and use mingw64/mingw-w64-x86_64-gcc 8.2.1+20181214-1 compiler package. Then I run ./configure with



./configure --pkg-config-flags=--static --disable-shared --enable-static




line - the best options I have googled at all my efforts. Then proceed with general



make
make install




sequence.



As a result, I get binaries that run smoothly in MSYS2 environment itself, but when I run it from host Windows explorer or cmd, first of all it ask for libbz2-1.dll, libiconv-2.dll and libwinpthread-1.dll libraries and when I put them in binaries' folder, they crash with "The application was unable to start correctly (0xc000007b)" error.



I've asked about this case at official https://ffmpeg.zeranoe.com/forum/viewtopic.php?f=5&t=6439 forum but still have no response for already 5 days.



Regarding dynamic linking libraries somehow I got bandaid solution with removing *.dll.a files from mingw64\x86_64-w64-mingw32\lib folder. But it looks not very clean for me. I wish to know if it is possible to do static linkage with some compiler/make/linker parameters or with editing ./configure or Makefile files somehow ?



Also 0xc000007b error still remaining.



I've managed to have desired result with media-autobuild_suite based on the same MSYS2 environment, so I know it is possible to do this somehow. But I'm very new to all this *nix things so don't understand it's bash script at all, not to mention it is pretty sophisticated by itself. The only thing I see it's producing correct ffmpeg executables running under native Windows environment not requiring dlls listed above.



According to all guides in internet I found at the moment, I should get standalone Windows executables with this toolset, but it just don't work and I'm stuck. Please, help.