Building Qt Multimedia from sources
This page describes the process of configuring and building Qt Multimedia. This description assumes familiarity with Building Qt Sources which specifies build requirements for your platform, as well as an overview of Qt Configure Options. For platform-specific considerations related to the Qt Multimedia module, see Platform Notes below.
Building from source
Building Qt Multimedia with full feature support depends on FFmpeg headers and libraries on most platforms. It is possible to build Qt Multimedia without the Qt Multimedia FFmpeg media backend, but this is only recommended when building for platforms where the FFmpeg backend is not supported.
FFmpeg developer libraries required to build Qt Multimedia can be built from sources or downloaded as binary packages. Qt Multimedia can use either static linking or dynamic linking to FFmpeg libraries. We recommend using the same major version of FFmpeg that is listed in FFmpeg as the default backend.
To build Qt Multimedia with FFmpeg support, specify the -DFFMPEG_DIR
CMake variable on the configure command line when building Qt. Note the --
separator which separates ordinary configure arguments from CMake parameters.
qt-source/configure -- -DFFMPEG_DIR=<FFMPEG_DIR>
Here, <FFMPEG_DIR>
is the directory containing the FFmpeg include, lib, and bin directories. To build Qt Multimedia without FFmpeg, omit the <FFMPEG_DIR>
variable or specify the -no-feature-ffmpeg
configure option.
If you prefer not to build all Qt's submodules, you can reduce configure and build times using the -submodules
configure option. This will configure a build that only builds Qt Multimedia and its dependencies.
qt-source/configure -submodules qtmultimedia -- -DFFMPEG_DIR=<FFMPEG_DIR>
If you configure Qt Multimedia against FFmpeg built with shared libraries (dynamic linking), the FFmpeg shared libraries must be in the module loader's search path to run tests or use examples.
Note: Qt Multimedia requires the FFmpeg avformat, avcodec, swresample, swscale, and avutil libraries during runtime to be able to use the FFmpeg media backend. If one or more of these dynamic libraries are not found during application startup, the FFmpeg media backend will fail to load, and the system will attempt to load the native backend. Qt Multimedia doesn't support as many features on native backends.
If you don't already have these libraries in the path
, specify the -DQT_DEPLOY_FFMPEG=ON
configure option. With this option enabled, the necessary FFmpeg binaries will be copied to Qt's install directory during the build and install steps:
qt-source/configure -submodules qtmultimedia -- -DFFMPEG_DIR=<FFMPEG_DIR> -DQT_DEPLOY_FFMPEG=ON
After configuring Qt Multimedia, carefully review the configure summary (found in the config.summary file). You can verify that FFmpeg is found under the "Plugin" section. Then follow the regular build and install steps described in Building Qt Sources.
Platform Notes
Linux
- When configuring Qt Multimedia with FFmpeg enabled, the pulseaudio development package is required. Without this package, FFmpeg will not be recognized.
- When using a version of FFmpeg that is built with VAAPI support, we recommend building Qt Multimedia with VAAPI support as well to make hardware texture conversion possible. To configure Qt Multimedia with VAAPI support, VAAPI developer libraries must be installed on your system. Review the config.summary file to verify that VAAPI support is enabled under the "Hardware acceleration and features" section.
- When configuring Qt Multimedia with the GStreamer backend, GStreamer v1.20 is the minimum requirement. However, we recommend using the latest stable GStreamer upstream release if possible.
© 2024 The Qt Company Ltd. Documentation contributions included herein are the copyrights of their respective owners. The documentation provided herein is licensed under the terms of the GNU Free Documentation License version 1.3 as published by the Free Software Foundation. Qt and respective logos are trademarks of The Qt Company Ltd. in Finland and/or other countries worldwide. All other trademarks are property of their respective owners.