Use command line argument --enable-ndk-translation64 for ARCVM setup
The availabilities of binary translation libraries for ARC++ are determined by Chrome OS build-time USE flags houdini, houdini64, ndk_translation, and ndk_translation64. The information of these flags is used by Chrome to properly set up the binary translation related properties for ARCVM. Previously, the information on the ndk_translation64 USE flag was not available for Chrome. However, by crrev.com/c/2219757 and crrev.com/c/2222062, Chrome OS now puts --enable-ndk-translation64 in Chrome's command line arguments iff the ndk_translation64 USE flag is set at build time. This CL makes Chrome properly handle this new information in the same way as that of the other USE flags. BUG=b:139480143 TEST=components_unittests TEST=Write/delete ndk_translation64 to/from DUT's /etc/ui_use_flags.txt. TEST=Restart UI and log in. TEST=Run getprop and confirm that the edit is properly reflected upon TEST=the property ro.boot.native_bridge. Change-Id: I74e180edbb128bd1410f2951eaaa6a52328c4f9c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2222240Reviewed-by:Ryo Hashimoto <hashimoto@chromium.org> Reviewed-by:
Yusuke Sato <yusukes@chromium.org> Commit-Queue: Youkichi Hosoi <youkichihosoi@chromium.org> Auto-Submit: Youkichi Hosoi <youkichihosoi@chromium.org> Cr-Commit-Position: refs/heads/master@{#779201}
Showing
Please register or sign in to comment