Advanced search

On other websites (3500)

• Evolution #3039 (Nouveau): Spip 2.1: prise en compte des champs_extra dans editer_artcile

  11 August 2013, by Arnaud Dupin de Beyssat

  Bonjour
  Après la création d’un formulaire Spip (sans usage de plugin) remplissant un article avec champs_extra, je me suis aperçu que les champs_extra n’étaient pas pris en compte.
  Après recherche, j’ai contaté que le pb venait du fichier action/editer_article qui limite la saisie aux champs Spip.
  Je l’ai donc patché en ajoutant les intitulés de mes champs extra, comme suit:

  function articles_set($id_article, $set=null)
  $err = ’’;
  // unifier $texte en cas de texte trop long
  trop_longs_articles();

  $c = array();<br />    foreach (array(<br />        'surtitre', 'titre', 'soustitre', 'descriptif',<br />        'nom_site', 'url_site', 'chapo', 'texte', 'ps'<br />//patch ADB        <br />        , 'latitude', 'longitude', 'cartes', 'zone_meteo', 'capitainerie', 'secours', 'freq_radio', 'distances', 'svce_meteo', 'jour', 'nuit', 'dangers', 'feux', 'acces', 'te', 'places', 'equipement', 'services', 'avitaillement', 'location', 'svce_divers', 'tourisme', 'mouillage', 'decor'<br />// fin patch ADB<br />    ) as $champ)<br />        $c[$champ] = _request($champ,$set);

  De ce fait les champs extra sont remplis.

  Serait-il possible, pour les Spip 2.1, de faire en sorte que les champs_extra existant éventuellement dans la table Articles soient automatiquement pris en compte?

  Merci

• fftools/ffmpeg: simplify output stream initialization call graph

  25 March 2023, by Anton Khirnov

  fftools/ffmpeg: simplify output stream initialization call graph
  Several places in the code currently call init_output_stream_wrapper(),
  
  which in turn calls init_output_stream(), which then calls either
  
  enc_open() or init_output_stream_streamcopy(), followed by
  
  of_stream_init(), which tells the muxer the stream is ready for muxing.
  All except one of these callers are in the encoding code, which will be
  
  moved to ffmpeg_enc.c. Keeping this structure would then necessitate
  
  ffmpeg_enc.c calling back into the common code in ffmpeg.c, which would
  
  then just call ffmpeg_mux, thus making the already convoluted call chain
  
  even more so.
  Simplify the situation by using separate paths for filter-fed output
  
  streams (audio and video encoders) and others (subtitles, streamcopy,
  
  data, attachments).
  

  • [DH] fftools/ffmpeg.c
  • [DH] fftools/ffmpeg_enc.c

• Linking to ffmpeg libraries fails while installing OpenCV

  12 August 2015, by Serhan

  FFMpeg 2.7.2 and all necessary libav* libraries are installed on my Ubuntu 14.04 machine. However, when I try to install OpenCV 2.4.11 (with FFMpeg enabled), I get the following error:

  /usr/bin/ld: cannot find -lavcodec
  
  /usr/bin/ld: cannot find -lswresample
  
  /usr/bin/ld: cannot find -lavutil
  
  /usr/bin/ld: cannot find -lavformat
  
  /usr/bin/ld: cannot find -lavcodec
  
  /usr/bin/ld: cannot find -lswresample
  
  /usr/bin/ld: cannot find -lavutil
  
  /usr/bin/ld: cannot find -lavformat
  
  collect2: error: ld returned 1 exit status
  
  make[2]: *** [bin/opencv_annotation] Error 1
  
  make[1]: *** [apps/annotation/CMakeFiles/opencv_annotation.dir/all] Error 2
  
  make: *** [all] Error 2

  I already tried pointing LD_LIBRARY_PATH and PKG_CONFIG_PATH to the locations which contain the FFmpeg libraries. I also tried with OpenCV 3.0 and obtained the same error.

  It seems that there is some kind of incompatibility between these versions of FFMpeg and OpenCV. Is there a workaround for this?

  EDIT:
  For example locate libavcodec.a outputs:

  /home/guel/cvpr2014/bin/dependencies/ffmpeg-2.4/libavcodec/libavcodec.a
  
  /home/guel/cvpr2014/bin/dependencies/lib/libavcodec.a
  
  /home/guel/cvpr2014/bin/dependencies/opencv-2.4.9/3rdparty/lib/libavcodec.a
  
  /home/guel/ffmpeg_build/lib/libavcodec.a
  
  /home/guel/git/ffmpeg/libavcodec/libavcodec.a
  
  /home/guel/mplayer/ffmpeg/libavcodec/libavcodec.a
  
  /home/guel/projects/mpegflow/dependencies/opencv-2.4.11/3rdparty/lib/libavcodec.a

  So, I have it in multiple places. Is that bad?