Recherche avancée

Sur d’autres sites (5383)

• avcodec/libx264 : add support for writing out CLL and MDCV

  11 mars 2023, par Jan Ekström

  avcodec/libx264 : add support for writing out CLL and MDCV
  Both of these two structures were first available with X264_BUILD
  
  163, so make relevant functionality conditional on the version
  
  being at least such.
  Keep handle_side_data available in all cases as this way X264_init
  
  does not require additional version based conditions within it.
  Finally, add a FATE test which verifies that pass-through of the
  
  MDCV/CLL side data is working during encoding.
  

  • [DH] configure
  • [DH] libavcodec/libx264.c
  • [DH] tests/fate/enc_external.mak
  • [DH] tests/ref/fate/libx264-hdr10

• avcodec/libx265 : add support for writing out CLL and MDCV

  11 mars 2023, par Jan Ekström

  avcodec/libx265 : add support for writing out CLL and MDCV
  The newer of these two are the separate integers for content light
  
  level, introduced in 3952bf3e98c76c31594529a3fe34e056d3e3e2ea ,
  
  with X265_BUILD 75. As we already require X265_BUILD of at least
  
  89, no further conditions are required.
  

  • [DH] libavcodec/libx265.c
  • [DH] tests/fate/enc_external.mak
  • [DH] tests/ref/fate/libx265-hdr10

• Configure error for ffmpeg 6.1 when executing in bash 5.0.17

  1er mars 2024, par user2715311

  I am trying to install ffmpeg 6.1 (https://ffmpeg.org/releases/ffmpeg-6.1.1.tar.xz), but when executing the configure script my bash version 5.0.17 removes the double quotes from the parameters containing the condition to select the version of the libraries being searched for to pass this parameter to pkg-config.

  


  For example, when processing code

  


  check_pkg_config libopenjpeg "libopenjp2 >= 2.1.0" openjpeg.h opj_version


  


  , the pkg-config call will look something like

  


  pkg-config --exists libopenjp2 >= 2.1.0


  


  As a result, configure execution stops with the following error.

  


  ERROR: libopenjp2 >= 2.1.0 not found using pkg-config


  


  As a hint, you may be prompted to set the path to the 2.1.0.pc file in PKG_CONFIG_PATH.

  


  It is interesting that this is the case in other versions of bash, for example, this problem is not observed in version 5.1.16.

  


  Does this mean that bash version 5.0.17 will actually not be able to work with configure to build most code sources, because such version selection conditions are used quite often when searching for the right libraries ?

  


  Or perhaps I can influence this bash behaviour in some way ? Or, alternatively, have I misinterpreted the problem at all and the solution is in a completely different area ?

  


  The problem was identified in the Linux Mint 20.1 distribution.

  


  $ lsb_release -a
No LSB modules are available.
Distributor ID: Linuxmint
Description:    Linux Mint 20.1
Release:    20.1
Codename:   ulyssa


  


  First of all, I checked that if I call pkg-config correctly, it can find the right library on my system.

  


  $ pkg-config --exists "libopenjp2 >= 2.1.0"
$ echo $?
0


  


  or

  


  $ pkg-config --cflags --libs "libopenjp2 >= 2.1.0"
-I/usr/include/openjpeg-2.3 -lopenjp2


  


  Next, I examined the configure code associated with this problem and came to the conclusion I outlined above.