Recherche avancée

Sur d’autres sites (6422)

• configure : Avoid requiring c99wrap for working around msys path issues

  14 novembre 2013, par Martin Storsjö

  configure : Avoid requiring c99wrap for working around msys path issues
  Msys is unable to convert unix style absolute paths to windows style
  
  paths when combined with certain multichar MSVC options such as
  
   Fo<file>. We used to work around this issue by passing them as two
  
  separate parameters separated by a space to c99wrap, which then mapped
  
  them back to the actual parameter format that MSVC uses.
  The only paths that actually are an issue are absolute unix style
  
  paths, and the only place such absolute paths are used with the output
  
  arguments (-Fo, -Fe, -Fi, -out :) are for the temp files within configure.
  By setting TMPDIR to . for msvc/icl builds, we never need to use
  
  absolute unix style paths for the file output, and we can use the
  
  actual proper form of the file output parameters. This avoids requiring
  
  the c99wrap wrapper for remapping the parameters for cases where the
  
  c99 converter isn’t invoked at all (MSVC2013 and ICL).
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DH] configure

• Android ffmpeg : Path with spaces

  13 avril 2015, par Javier Manzano

  I have almost the same problem that this question : Android : ffmpeg with filenames containing spaces

  The problem is I’m using this library : https://github.com/hiteshsondhi88/ffmpeg-android-java

  In the stack overflow question that I’ve post the only way to achieve is passing the cmd command as String[] (which cannot be done with this library)

• How to set path to Opus on Heroku

  19 décembre 2016, par onnex

  Hi I’m stuck on getting opuslib to work on Heroku. I’ve installed the opus library buildback here https://elements.heroku.com/buildpacks/dubsmash/heroku-buildpack-opus

  However my app throws an error Error in command 'play' - OpusNotLoaded: I’m assuming my app is not detecting the opus buildpack. This is where I get stuck

  From uploading changes to my repo the log shows

  remote: ----------------------------------------------------------------------
  
  remote: Libraries have been installed in:
  
  remote:    /tmp/build_b191a43c9f4f1541f35409377bad92ed/libopus/build/lib
  
  remote:
  
  remote: If you ever happen to want to link against installed libraries
  
  remote: in a given directory, LIBDIR, you must either use libtool, and
  
  remote: specify the full pathname of the library, or use the `-LLIBDIR'
  
  remote: flag during linking and do at least one of the following:
  
  remote:    - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
  
  remote:      during execution
  
  remote:    - add LIBDIR to the `LD_RUN_PATH' environment variable
  
  remote:      during linking
  
  remote:    - use the `-Wl,-rpath -Wl,LIBDIR' linker flag
  
  remote:    - have your system administrator add LIBDIR to `/etc/ld.so.conf'
  
  remote:
  
  remote: See any operating system documentation about shared libraries for
  
  remote: more information, such as the ld(1) and ld.so(8) manual pages.
  
  remote: ----------------------------------------------------------------------
  
  remote: make[4]: Entering directory `/tmp/build_b191a43c9f4f1541f35409377bad92ed/libopus/opus-1.1/doc'
  
  remote: make[5]: Entering directory `/tmp/build_b191a43c9f4f1541f35409377bad92ed/libopus/opus-1.1/doc'
  
  remote: make[5]: Nothing to be done for `install-exec-am'.
  
  remote: make[5]: Nothing to be done for `install-data-am'.
  
  remote: make[5]: Leaving directory `/tmp/build_b191a43c9f4f1541f35409377bad92ed/libopus/opus-1.1/doc'
  
  remote: make[4]: Leaving directory `/tmp/build_b191a43c9f4f1541f35409377bad92ed/libopus/opus-1.1/doc'
  
  remote:  /bin/mkdir -p '/tmp/build_b191a43c9f4f1541f35409377bad92ed/libopus/build/share/aclocal'
  
  remote:  /usr/bin/install -c -m 644 opus.m4 '/tmp/build_b191a43c9f4f1541f35409377bad92ed/libopus/build/share/aclocal'
  
  remote:  /bin/mkdir -p '/tmp/build_b191a43c9f4f1541f35409377bad92ed/libopus/build/lib/pkgconfig'
  
  remote:  /usr/bin/install -c -m 644 opus.pc '/tmp/build_b191a43c9f4f1541f35409377bad92ed/libopus/build/lib/pkgconfig'
  
  remote:  /bin/mkdir -p '/tmp/build_b191a43c9f4f1541f35409377bad92ed/libopus/build/include/opus'
  
  remote:  /usr/bin/install -c -m 644 include/opus.h include/opus_multistream.h include/opus_types.h include/opus_defines.h '/tmp/build_b191a43c9f4f1541f35409377bad92ed/libopus/build/include/opus'
  
  remote: make[3]: Leaving directory `/tmp/build_b191a43c9f4f1541f35409377bad92ed/libopus/opus-1.1'
  
  remote: make[2]: Leaving directory `/tmp/build_b191a43c9f4f1541f35409377bad92ed/libopus/opus-1.1'
  
  remote: make[1]: Leaving directory `/tmp/build_b191a43c9f4f1541f35409377bad92ed/libopus/opus-1.1'
  
  remote: -----> Python app detected
  
  remote:      $ pip install -r requirements.txt
  
  remote:
  
  remote: -----> ffmpeg app detected
  
  remote: -----> Installing ffmpeg, ffmpeg-10bit, ffprobe, ffserver and qt-faststart ...
  
  remote:        exporting PATH
  
  remote: -----> Discovering process types
  
  remote:        Procfile declares types -> worker
  
  remote:
  
  remote: -----> Compressing...
  
  remote:        Done: 220.2M

  How would I set my library so my app can detect opus ? Your help would be greatly appreciated.