Recherche avancée

Sur d’autres sites (5680)

• Révision 23269 : simples quotes, définir $valeurs et PSR

  15 novembre 2016, par kent1@arscenic.info

• configure : Include quotes around pkg_version

  16 décembre 2024, par Joe Schiffler

  configure : Include quotes around pkg_version
  In some MSYS environments it can happen that the 3 argument syntax
  
  for pkg-config library specifications fails because somehow the
  
  expansion of pkg_version ends up with a redirection we guess.
  To avoid failures like in the referenced build[2], we quote it
  
  so the whole module including operators will be expanded into
  
  a single shell word and the single argument syntax for specifying
  
  the library for pkg-config will be used.
  The single argument syntax seems to be supported by the original
  
  pkg-config from the beginning more than 20 years[3].
  In the pkgconf implementation single argument syntax was supported
  
  pretty much from the beginning as well. The multiple argument syntax
  
  we used until this change, was not supported until a change[4] more
  
  than 10 years ago.
  References
  
  1. Build passing with quotes :
  
     https://github.com/JoeSchiff/pyav-ffmpeg/actions/runs/12358403929
  
  2. Build failing without quotes :
  
     https://github.com/JoeSchiff/pyav-ffmpeg/actions/runs/12360472377
  
  3. Earliest commit of the current pkg-config Git repo already mentions the single argument syntax :
  
     https://gitlab.freedesktop.org/pkg-config/pkg-config/-/commit/2ac96cbcc708d8945329fd1b2001386e1c895c64#124c0becfe68b1ef671f49ed2b9d24779ace126f_0_162
  
  4. pkgconf gets support for 3 argument syntax (pkgconf —exists liba = 1.2.3) :
  
     https://github.com/pkgconf/pkgconf/commit/793de6a06ca52fbfe906a269b5f2b2ba41739517
  Commit-message-by : Alexander Strasser <eclipse7@gmx.net>
  
  Signed-off-by : Joe Schiffler <joeschiffler3@gmail.com>
  
  Signed-off-by : Alexander Strasser <eclipse7@gmx.net>
  

  • [DH] configure

• FFmpeg chokes on filenames inside of quotes w/ whitespaces [duplicate]

  18 février 2016, par user3578907

  This question already has an answer here :

  • Script fails with spaces in directory names
    
    1 answer
    

  I’m trying to convert all of my FLACs in to MP3s. Each artist has a folder, and each album has a subfolder. I used the find command to compile a clean list of all of the FLACs in to a file called songlist, and tried dumping it in to FFmpeg with

  (for SONG in `cat songlist` ; do ffmpeg -i "$SONG" -f mp3 -ab 256000 "`basename "$SONG" .flac`.mp3" || break; done)

  Any time ffmpeg reaches a file with a space or special character it interprets it directly. I don’t understand why, as I thought the quotes around $SONG would sanitize it enough. Any thoughts on how to accomplish this task more efficiently or how to fix my code are welcomed.

  songlist is just filled with full paths to the files. No quotes around the paths.