
Recherche avancée
Autres articles (41)
-
La file d’attente de SPIPmotion
28 novembre 2010, parUne file d’attente stockée dans la base de donnée
Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...) -
Contribute to documentation
13 avril 2011Documentation is vital to the development of improved technical capabilities.
MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
To contribute, register to the project users’ mailing (...) -
Selection of projects using MediaSPIP
2 mai 2011, parThe examples below are representative elements of MediaSPIP specific uses for specific projects.
MediaSPIP farm @ Infini
The non profit organizationInfini develops hospitality activities, internet access point, training, realizing innovative projects in the field of information and communication technologies and Communication, and hosting of websites. It plays a unique and prominent role in the Brest (France) area, at the national level, among the half-dozen such association. Its members (...)
Sur d’autres sites (6695)
-
Evolution #3958 : Mise à jour de la liste des types mines
12 juin 2017, par nico d_Hop, pour information ce sont les type MIME, pas mines :)
Type mine c’est pour les voitures ^^
https://fr.wikipedia.org/wiki/Type_MIMEEt sinon, ils sont indiqués ici dans le tableau apparemment :
https://en.wikipedia.org/wiki/High_Efficiency_Image_File_Format#Brands_and_MIME_types -
Removing executable permissions from all files.
4 août 2011m .gitignore m README.rdoc m build.xml m demo/360-player/360 button - large.psd m demo/360-player/360 button.psd m demo/360-player/360-button-pause-light.gif m demo/360-player/360-button-pause-light.png m demo/360-player/360-button-pause.gif m demo/360-player/360-button-pause.png m (...)
-
Compile FFmpeg project for ARM in PC Linux 64-bits
4 avril 2017, par Dang_HoI want to compile a simple FFmpeg project for my Arrow Sockit Board with an arm-linux-gnueabihf architecture from my Linux-64bit PC. I don’t want to compile the project in the board directly because of my low CPU and that is not convenient for me.
I’m using
FFmpeg version 2.8.11
and this is myMakefile
and my"main.c"
. I know, myMakefile
has something wrong in it. If I command"make"
, it will compile depending on my PC’s architecture, I can’t use that binary file on my board. So, can someone please tell me how to do it.I Cross-Compiled the FFmpeg package and installed into the board. I tested all functions such as ffmpeg, ffplay. All them work. The source code folder is located to /home/hohaidang/ffmpeg-2.8.11
#include
#include <libavcodec></libavcodec>avcodec.h>
#include <libavformat></libavformat>avformat.h>
#include <libswscale></libswscale>swscale.h>
int main(int argc, char *argv[]){
av_register_all();
return 0;
}# use pkg-config for getting CFLAGS and LDLIBS
FFMPEG_LIBS= libavdevice \
libavformat \
libavfilter \
libavcodec \
libswresample \
libswscale \
libavutil \
CFLAGS += -Wall -g
CFLAGS := $(shell pkg-config --cflags $(FFMPEG_LIBS)) $(CFLAGS)
LDLIBS := $(shell pkg-config --libs $(FFMPEG_LIBS)) $(LDLIBS)
EXAMPLES= main
OBJS=$(addsuffix .o,$(EXAMPLES))
# the following examples make explicit use of the math library
avcodec: LDLIBS += -lm
decoding_encoding: LDLIBS += -lm
muxing: LDLIBS += -lm
resampling_audio: LDLIBS += -lm
.phony: all clean-test clean
all: $(OBJS) $(EXAMPLES)
clean-test:
$(RM) test*.pgm test.h264 test.mp2 test.sw test.mpg
clean: clean-test
$(RM) $(EXAMPLES) $(OBJS)