Zen

Translation

English type: Plain text
On different build machines, different NDK paths and different paths to the project (and thus to its `jni` directory) are used. This leads to different paths to the source files in debug symbols, causing the linker to generate a different _build-id_, which is preserved after stripping.
91/2870 · 287

Sign in to save the translation.

English Chinese (Simplified) Actions
Embedded [timestamps](https://reproducible-builds.org/docs/timestamps/) are the most common source of reproducibility issues and are best avoided.
内嵌的[时间戳](https://reproducible-builds.org/docs/timestamps/)是可重复性问题最常见的来源，最好避免。
Native library stripping
本地库的剥离
It seems that the stripping of native libraries, e.g. `libfoo.so`, can cause intermittent reproducibility issues. It is important to use the exact NDK version when rebuilding, e.g. `r21e`. Disabling stripping can sometimes help. Gradle seems to strip shared libraries by default, even the app is receiving the shared libraries via an AAR library. Here is how to disable it in Gradle:
似乎剥离原生库，例如 `libfoo.so`，可能会导致间歇性重现性问题。重建时使用确切的 NDK 版本很重要，例如 `r21e`。禁用剥离有时会有所帮助。 Gradle 似乎默认剥离共享库，甚至应用也通过 AAR 库接收共享库。以下是在 Gradle 中禁用它的方法：
android {
packagingOptions {
doNotStrip '**/*.so'
}
}
android {
packagingOptions {
doNotStrip '**/*.so'
}
}
NDK _build-id_
NDK _build-id_
On different build machines, different NDK paths and different paths to the project (and thus to its `jni` directory) are used. This leads to different paths to the source files in debug symbols, causing the linker to generate a different _build-id_, which is preserved after stripping.
在不同的构建机器上，使用不同的 NDK 路径和不同的项目路径（及其 `jni` 目录）。 这导致调试符号中源文件的路径不同，造成该链接器生成不同的_build-id_，剥离后保留。
One possible solution is passing `--build-id=none` to the linker which will disable _build-id_ generation completely.
一个可能的解决方案是传递 `--build-id=none` 到链接器，这会彻底禁止生成 _build-id_ 。
NDK hash style
NDK 哈希样式
LLVM passes different defaults to linkers on different platforms. After [this commit](https://github.com/llvm/llvm-project/commit/95dcaef00379e893dabc61cf598fe51c9d03414e#diff-061e3e32cfa3dd06717856cc16465106a3b72520eb9b0c2954513f194bd1696f) was merged into the NDK, `--hash-style=gnu` will be used on Debian by default. To change the hash style, `--hash-style=gnu` can be passed to the linker.
LLVM 在不同平台上传递给链接器的默认值也是不同的。在[此提交](https://github.com/llvm/llvm-project/commit/95dcaef00379e893dabc61cf598fe51c9d03414e#diff-061e3e32cfa3dd06717856cc16465106a3b72520eb9b0c2954513f194bd1696f) 被合并入 NDK 后， `--hash-style=gnu` 默认用于 Debian。要更改哈希样式，可以传递 `--hash-style=gnu`到链接器。
_platform_ Revisions
_platform_ 修订版
In 2014, the Android SDK tools [were changed](https://issuetracker.google.com/issues/37132313) to [stick two](https://android.googlesource.com/platform/frameworks/base/+/ad2d07d%5E!/) [data elements](https://android.googlesource.com/platform/frameworks/base/+/5283fab%5E!/) in `AndroidManifest.xml` as part of the build process: `platformBuildVersionName` and `platformBuildVersionCode`. `platformBuildVersionName` includes the "revision" of the _platform_ package built against (e.g. `android-23`), however different "revisions" of the same _platform_ package cannot be installed in parallel. Plus the SDK tools do not support specifying the required revision as part of the build process. This often results in an otherwise reproducible build where the only difference is the `platformBuildVersionName` attribute.
Android SDK 工具在2014年[改为](https://issuetracker.google.com/issues/37132313)在构建过程中在 `AndroidManifest.xml` 中 [添加两个](https://android.googlesource.com/platform/frameworks/base/+/ad2d07d%5E/)[数据元素](https://android.googlesource.com/platform/frameworks/base/+/5283fab%5E/)：`platformBuildVersionName` 和 `platformBuildVersionCode`。`platformBuildVersionName` 包括 _platforms_ 包的"修订版"，根据该包构建（例如：`android-23`），然而同一 _platforms_ 包的不同"修订版"不能并行安装。 另外，SDK 工具不支持指定所需的修订作为构建过程的一部分。 这往往会导致另一种可重复构建，它和真正可重复构建之间唯一的区别是 `platformsBuildVersionName` 属性。

Loading…

User avatar None

String updated in the repository

  1. F-Droid
  2. Website Docs
  3. Chinese (Simplified)
On different build machines, different NDK paths and different paths to the project (and thus to its `jni` directory) are used. This leads to different paths to the source files in debug symbols, causing the linker to generate a different _build-id_, which is preserved after stripping.
在不同的构建机器上，使用不同的 NDK 路径和不同的项目路径（及其 `jni` 目录）。 这导致调试符号中源文件的路径不同，造成该链接器生成不同的_build-id_，剥离后保留。
a year ago
User avatar deleted-13019

Translation changed

  1. F-Droid
  2. Website Docs
  3. Chinese (Simplified)
On different build machines, different NDK paths and different paths to the project (and thus to its `jni` directory) are used. This leads to different paths to the source files in debug symbols, causing the linker to generate a different _build-id_, which is preserved after stripping.
在不同的构建机器上，使用不同的 NDK 路径和不同的项目路径（及其 `jni` 目录）。 这导致调试符号中源文件的路径不同，导致造成该链接器生成不同的_build-id_，剥离后保留。
a year ago
User avatar deleted-13019

Translation changed

  1. F-Droid
  2. Website Docs
  3. Chinese (Simplified)
On different build machines, different NDK paths and different paths to the project (and thus to its `jni` directory) are used. This leads to different paths to the source files in debug symbols, causing the linker to generate a different _build-id_, which is preserved after stripping.
在不同的构建机器上，使用不同的 NDK 路径和不同的项目路径（及其 _jni_`jni` 目录）。这导致调试符号中源文件的路径不同，导致该链接器生成不同的_build-id_，剥离后保留。
a year ago
User avatar deleted-13019

Translation changed

  1. F-Droid
  2. Website Docs
  3. Chinese (Simplified)
On different build machines, different NDK paths and different paths to the project (and thus to its `jni` directory) are used. This leads to different paths to the source files in debug symbols, causing the linker to generate a different _build-id_, which is preserved after stripping.
在不同的构建机器上，使用不同的 NDK 路径和不同的项目路径（因此到及其 _jni_ 目录）。这导致调试符号中源文件的路径不同，导致该链接器生成不同的_build-id_，剥离后保留。
a year ago
User avatar None

String updated in the repository

  1. F-Droid
  2. Website Docs
  3. Chinese (Simplified)
On different build machines, different NDK paths and different paths to the project (and thus to its `jni` directory) are used. This leads to different paths to the source files in debug symbols, causing the linker to generate a different _build-id_, which is preserved after stripping.
在不同的构建机器上，使用不同的 NDK 路径和不同的项目路径（因此到其 _jni_ 目录）。这导致调试符号中源文件的路径不同，导致链接器生成不同的_build-id_，剥离后保留。
a year ago
User avatar None

Source string changed

  1. F-Droid
  2. Website Docs
  3. Chinese (Simplified)
On different build machines, different NDK paths and different paths to the project (and thus to its _jni_`jni` directory) are used. This leads to different paths to the source files in debug symbols, causing the linker to generate a different _build-id_, which is preserved after stripping.
a year ago
Browse all string changes

Things to check

Markdown syntax

Markdown syntax does not match source

Reset

Glossary

English Chinese (Simplified)
build 构建 F-Droid Glossary
source 源代码 F-Droid Glossary

String information

Source string description
type: Plain text
Flags
md-text
Source string location
_docs/Reproducible_Builds.md
String age
a year ago
Last updated
11 months ago
Source string age
a year ago
Translation file
po/_docs.zh_Hans.po, string 1556