Zen

Source string Source string

547/10000 · 547

The string is read only.

English Actions
Qt projects can use [rcc](https://doc.qt.io/qt-5/rcc.html) to embed resources such as translations and images. Since Qt 5.8, rcc includes the file modification time of source files in the build output. This is especially problematic for translation files that are generated at build time. Possible workarounds:
(Since Qt 5.9) If a project does not rely on an accurate [QFileInfo::lastModified](https://doc.qt.io/qt-5/qfileinfo.html#lastModified), pass `--format-version 1` to `rcc`. If [`AUTORCC`](https://cmake.org/cmake/help/latest/prop_tgt/AUTORCC.html) is enabled, this can be done by setting [`CMAKE_AUTORCC_OPTIONS`](https://cmake.org/cmake/help/latest/variable/CMAKE_AUTORCC_OPTIONS.html) to `--format-version;1`. Upstream projects are encouraged to do this after checking that Qt 5.9 or newer is in use.
(Since Qt 5.11) Set the `QT_RCC_SOURCE_DATE_OVERRIDE` environment variable which behaves similar to [`SOURCE_DATE_EPOCH`](https://reproducible-builds.org/specs/source-date-epoch/).
(Since Qt 5.13) Set the `SOURCE_DATE_EPOCH` environment variable.
Ensure that generated source files are touched with a fixed timestamp before rcc is called. See also <https://bugs.debian.org/894476>.
Qt projects that use `Q_OBJECT` macros require [moc](https://doc.qt.io/qt-5/moc.html) to generate additional C++ files. CMake will automatically do this when [`AUTOMOC`](https://cmake.org/cmake/help/latest/prop_tgt/AUTOMOC.html) is enabled, but then the relative path from the build directory to the source directory will become part of the build environment. For example, if the build directory is `/tmp/build` and the source file is at `/tmp/foo/widget.h`, then the generated file will include `../[...]/../foo/widget.h`. Possible workarounds:
Use the `-p` option to override the include prefix. This requires the prefix plus the header filename to be available from the include path. See also <https://gitlab.kitware.com/cmake/cmake/issues/18815>.
Ensure that the build directory and source directory remains fixed across builds. For example, if users always create a `build` directory in the source tree, then reproducibility won't be affected.
Disclaimer
Not all problems have solutions currently. Some tools that might be used in a build process might require fixes to become non-deterministic. The Debian effort keeps a list of [all issues found](https://reproducible.debian.net/index_issues.html) while investigating reproducibility problems in its 22,000+ source packages. While some require changes in the package source itself, some can be fixed by improving or fixing the tools used to perform the builds.
Embedded signatures

Loading…

No matching activity found.
Browse all string changes

Things to check

Ellipsis

The string uses three dots (...) instead of an ellipsis character (…)

Reset

Glossary

English English
No related strings found in the glossary.

String information

Source string description
type: Bullet: ' * '
Flags
md-text, read-only
Source string location
_docs/deterministic_build_systems.md
String age
2 years ago
Last updated
a year ago
Source string age
2 years ago
Translation file
po/_docs.pot, string 173