
Recherche avancée
Médias (1)
-
Bug de détection d’ogg
22 mars 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Video
Autres articles (40)
-
Submit enhancements and plugins
13 avril 2011If 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. -
La sauvegarde automatique de canaux SPIP
1er avril 2010, parDans le cadre de la mise en place d’une plateforme ouverte, il est important pour les hébergeurs de pouvoir disposer de sauvegardes assez régulières pour parer à tout problème éventuel.
Pour réaliser cette tâche on se base sur deux plugins SPIP : Saveauto qui permet une sauvegarde régulière de la base de donnée sous la forme d’un dump mysql (utilisable dans phpmyadmin) mes_fichiers_2 qui permet de réaliser une archive au format zip des données importantes du site (les documents, les éléments (...) -
Script d’installation automatique de MediaSPIP
25 avril 2011, parAfin de palier aux difficultés d’installation dues principalement aux dépendances logicielles coté serveur, un script d’installation "tout en un" en bash a été créé afin de faciliter cette étape sur un serveur doté d’une distribution Linux compatible.
Vous devez bénéficier d’un accès SSH à votre serveur et d’un compte "root" afin de l’utiliser, ce qui permettra d’installer les dépendances. Contactez votre hébergeur si vous ne disposez pas de cela.
La documentation de l’utilisation du script d’installation (...)
Sur d’autres sites (6430)
-
How to build static library based on existing Live555+FFmpeg
30 mars 2016, par SCKI am trying to build an .a static library (named foo.a) based on Live555 & FFmpeg.
So that my OS X app can use foo.a to do RTSP streaming.
If my app use live555 and/or FFmpeg directly, it works great
.Picture1, but I don’t want to use them directly, that’s why I’m trying to build foo.aIf I build foo.a that wraps live555.a and my custom source code, it also works too.
But If I build foo.a that wraps live555.a and ffmpeg and my custom source code
Picture2When I build OS X app (which is now using foo.a), I got the following error :
Undefined symbols for architecture x86_64 : "avcodec_version()",
referenced from : startStreaming() in libFoo.a(Facade.o) ld : symbol(s)
not found for architecture x86_64 clang : error : linker command failed
with exit code 1 (use -v to see invocation)Any suggestions would be appreciated !
-
MobileVlcKit compiling Failed
25 février 2016, par BittooHi i am trying to use MobileVLCKit.For that i am using cocoapads like below
pod ’MobileVLCKit’pod 'MobileVLCKit'
then i compile my project it is showing plenty of errors below is my error Log
NOTE: a missing vtable usually means the first non-inline virtual member function has no definition.
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
"std::basic_string, std::allocator >::find(wchar_t const*, unsigned long, unsigned long) const", referenced from:
TagLib::String::find(TagLib::String const&, int) const in MobileVLCKit(tstring.cpp.o)
TagLib::String::split(TagLib::String const&) const in MobileVLCKit(tstring.cpp.o)
dash::mpd::BasicCMParser::parseCommonAttributesElements(dash::xml::Node*, dash::mpd::CommonAttributesElements*, dash::mpd::CommonAttributesElements*) const in MobileVLCKit(libdash_plugin_la-BasicCMParser.o)I tried with architecture x86_64 but still showing lot of errors. I don’t know how to clear these errors.so can any body please help me
-
We are hiring engineers to build an awesome product and platform used by millions of people
16 février 2016, par Piwik Core Team — JobsAre you ready for a new challenge ? Or maybe you know someone who is looking for a change ? We have some exciting problems to solve and are looking for senior developers to work with us and our community on our open source Piwik Analytics platform. Piwik is used by more than one million websites all over the world. It is deployed on more than 300.000 servers and some users track more than 1 billion actions per month.
What is it like to work on Piwik ?
We develop this software using modern PHP, MySQL, Redis, AngularJS and more. We provide several kind of APIs and a plugin architecture to allow developers to extend and change Piwik to their needs. However, we would not be Piwik if we stopped at this point ! We want to turn Piwik into an even more awesome product and platform.
You can imagine there is a lot to do and many challenges to face !While one part is to always make Piwik scale better and to improve UI and UX, we also want to provide simple APIs to make the life of developers as pleasant as possible. We aim to solve things the right way and our thousands of unit, integration, system, JavaScript and screenshot tests help us to innovate and to not be afraid of change. We like clean code and constant improvements.
The Piwik team lives in New Zealand, Europe (Poland, Germany) and in the U.S. We do the vast majority of our collaboration online. Our values include being open, transparent and sharing knowledge. For this we use tools like GitHub and Slack to communicate and Quake servers to take our minds off complex challenges. We are a small, flexible team, so when you come aboard, you will play an integral part in engineering and have a big impact on the product loved by so many people. You’ll help to create a welcoming environment for new contributors and set an example with your development practices and communications skills.
Apply now, or spread the word !
If you have strong skills in PHP send us an email with your CV and tell us a little about yourself and your experience in engineering complex applications.
Apply for a job here http://piwik.org/jobs/ and if you’re maybe not the right candidate, contribute to the project by sharing this blog post and by sending it to your friends !