Testing ffmpeg 5

Gilles Caulier caulier.gilles at gmail.com
Mon Sep 19 04:49:01 BST 2022


Hi Steven,

This means that Gitlab Windows CI docker does not follow settings from
binary factory tooling now.

Why ? Probably since the build factory (old CI) was shut down a few
weeks ago from KDE infrastructure in favor of gitab, the way to
configure the CI docker has changed.

This is not the case of the binary factory (current CD) from KDE
infrastructure which has not yet migrated to gitlab, but it's just a
question of time.

Where is the CI configuration now ? I don't know. as nothing is documented...

Gilles

Le lun. 19 sept. 2022 à 00:01, Steven Robbins <steve at sumost.ca> a écrit :
>
> Hey -- just noticed that the windows machine is running FFMEG 5:
>
> -- FFMpeg AVCodec    (required) : TRUE (59.18.100)
> -- FFMpeg AVDevice   (required) : TRUE (59.4.100)
> -- FFMpeg AVFilter   (required) : TRUE (8.24.100)
> -- FFMpeg AVFormat   (required) : TRUE (59.16.100)
> -- FFMpeg AVUtil     (required) : TRUE (57.17.100)
> -- FFMpeg SWScale    (required) : TRUE (6.4.100)
> -- FFMpeg SWResample (required) : TRUE (4.3.100)
> -- FFMpeg AVResample (optional) : FALSE ()
> -- MediaPlayer support is enabled                       : yes
> -- MediaPlayer will use FFMpeg 5 API                    : yes
>
> So we already have a test runner :-)
>
> -Steve


More information about the Digikam-devel mailing list