Recherche avancée

Sur d’autres sites (4884)

• Evolution #3279 : Connaitre la profondeur d’inclusion dans le pipeline styliser

  4 octobre 2014, par cedric -

  Au moins pourrait-on distinguer l’appel initial du fond principal des inclusions, ce qui est assez simple.
  Pour le cas du plugin intranet il faut lister le inc-head dans les pages autorisées, mais si rigoureusement ce n’en est pas une. Cela dit cela permet après d’accèder directement à ce head pour tout article ou autre et peut-être de divulguer du contenu. Dans ce cas je pense que le / qui sert dans la detection implique aussi qu’un fond qui contient un / ne peux pas etre vu directement par une url de type ?page=...

• How to compile c99-to-c89 convertor with clang ?

  27 septembre 2016, par theateist

  I’m trying to compile ffmpeg in windows for VisualStudio and one of the step is to compile c99-to-c89 code with clang according to this post. I managed to create clang.exe but how I compile c99-to-c89 code with it ?

  I changed a little bit the makefile in c99-to-c89 so CC variable points now to clang.exe compiler and not cl.exe

  EXT=.exe
  
  
  
  all: c99conv$(EXT) c99wrap$(EXT)
  
  
  
  CLANGDIR=C:/build
  
  CC=C:/build/bin/Release/clang.exe
  
  CFLAGS=-nologo -Z7 -D_CRT_SECURE_NO_WARNINGS=1 -Dpopen=_popen -Dunlink=_unlink -Dstrdup=_strdup -Dsnprintf=_snprintf -I. -I$(CLANGDIR)/tools/clang/include
  
  LDFLAGS=-nologo -Z7 $(CLANGDIR)/lib/Release/libclang.lib
  
  
  
  clean:
  
      rm -f c99conv$(EXT) c99wrap$(EXT) convert.o compilewrap.o
  
      rm -f unit.c.c unit2.c.c
  
  
  
  test1: c99conv$(EXT)
  
      $(CC) -P unit.c -Fiunit.prev.c
  
      ./c99conv unit.prev.c unit.post.c
  
      diff -u unit.{prev,post}.c
  
  
  
  test2: c99conv$(EXT)
  
      $(CC) -P unit2.c -Fiunit2.prev.c
  
      ./c99conv unit2.prev.c unit2.post.c
  
      diff -u unit2.{prev,post}.c
  
  
  
  test3: c99conv$(EXT)
  
      $(CC) $(CFLAGS) -P -Ficonvert.prev.c convert.c
  
      ./c99conv convert.prev.c convert.post.c
  
      diff -u convert.{prev,post}.c
  
  
  
  c99conv$(EXT): convert.o
  
      $(CC) -Fe$@ $< $(LDFLAGS) $(LIBS)
  
  
  
  c99wrap$(EXT): compilewrap.o
  
      $(CC) -Fe$@ $< $(LDFLAGS)
  
  
  
  %.o: %.c
  
      $(CC) $(CFLAGS) -Fo$@ -c $<

  but when I run make command I get clang: error: unsupported use of internal gcc -Z option '-Z7'. I guess the problem in CFLAGS and LDFLAGS but I don’t know how to fix it because the lack of knowledge in makefile and clang.

• Can you make fluent-ffmpeg use a copy of ffmpeg running inside a Docker container ?

  1er septembre 2020, par Bdyce

  I have some nodejs code in a folder on a host machine that has an npm module that requires an environment variable to be set in order to utilize an executable called FFmpeg. I have a containerized FFmpeg along with its dependencies for development purposes and am now wondering how I am able to specify the path to the FFmpeg executable from the host machine in order for this npm module to function correctly.

  


  I have the idea to use a docker volume that exposes the executable from the container onto the host and then to set the environment variable using that path but I'm not sure if this will work.

  


  Some notes from the module's docs.

  


  


  If the FFMPEG_PATH environment variable is set, fluent-ffmpeg will use it as the full path to the ffmpeg executable. Otherwise, it will attempt to call ffmpeg directly (so it should be in your PATH). You must also have ffprobe installed (it comes with ffmpeg in most distributions). Similarly, fluent-ffmpeg will use the FFPROBE_PATH environment variable if it is set, otherwise it will attempt to call it in the PATH.