chromium/src
0
Fork 0
Code Activity

ios: Update comments on nasm.

Browse Source 
nasm emits LC_BUILD_VERSION [1] , so it is compatible with builds with
bitcode enabled.

[1] https://crrev.com/c/3048213

Bug: 1145197
Change-Id: I1c55a14bc4721edad14fd1da231543252b9c5512
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3093953
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#913038}
This commit is contained in:
Byoungchan Lee
2021-08-18 17:00:58 +00:00
committed by Chromium LUCI CQ
parent 92c02815a0
commit e856c3ada7
1 changed files with 0 additions and 5 deletions

5
build/config/ios/BUILD.gn

@ -16,11 +16,6 @@ declare_args() {
# Mimicking how Xcode handles it, the production builds (is_debug = false)
# get real bitcode sections added, while the debug builds (is_debug = true)
# only get bitcode-section "markers" added in them.
# NOTE: This option is ignored when building versions for the iOS simulator,
# where a part of libvpx is compiled from the assembly code written using
# Intel assembly syntax; Yasm / Nasm do not support emitting bitcode parts.
# That is not a limitation for now as Xcode mandates the presence of bitcode
# only when building bitcode-enabled projects for real devices (ARM CPUs).
enable_ios_bitcode = false
}