Hi! In my opinion we can wait branching & integrate this in 'dev' after it. And pick changes in '6.8' after beta1; it is more important to keep CI & provisioning as stable as possible this close to feature freeze to make sure we can keep FF schedule (and so on Qt 6.8.0 final schedule as well) and get Beta1 out before summer vacations starts...
br, Jani > -----Original Message----- > From: Development <development-boun...@qt-project.org> On Behalf Of > Jøger Hansegård via Development > Sent: tiistai 21. toukokuuta 2024 18.53 > To: development@qt-project.org > Subject: [Development] Provisioning freeze exception for building FFmpeg as > shared libraries > > Hi, > > I would like to request a provisioning freeze exception for building FFmpeg as > shared libraries. > > The goal of this change is to make it easier to transition Qt Multimedia > applications from legacy native media backends to the default FFmpeg media > backend. > > Although the FFmpeg media backend can still be built with static linking to > FFmpeg, we will switch to dynamic linking against FFmpeg for binaries > deployed by the Qt Online Installer. This is already released for Windows in > Qt > 6.7 and will be implemented for all platforms in Qt 6.8. > > FFmpeg is built as part of provisioning, and the corresponding scripts must > therefore be updated to build FFmpeg as shared libraries on the remaining > platforms, iOS, Linux, and Android. > > * https://bugreports.qt.io/browse/QTBUG-120990 > * https://bugreports.qt.io/browse/QTBUG-120991 > * https://bugreports.qt.io/browse/QTBUG-122010 > > Since the change has implications for application deployment, we depend on > getting early feedback on the change, and if possible, as part of beta 1. > > Best regards, > Jøger Hansegård > -- > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
