SuperSize: Use the combined native library for analysis where needed
With native feature modules, generation of the main library (and feature libraries) is a two-step process: 1. Link a single, combined library (with partitions inside it) 2. Use llvm-objcopy to split out the main lib and feature libs This implies that: - libchrome.so's ninja inputs are not .o and .a files - The .map file now relates to the combined library, not the partitions, although it can naturally be used to analyze the partitions. Bug: 982334 Change-Id: I345f618f30639e7637ee905776a50c9cf5686773 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1708204 Commit-Queue: Christopher Grant <cjgrant@chromium.org> Reviewed-by:Samuel Huang <huangs@chromium.org> Cr-Commit-Position: refs/heads/master@{#680169}
Showing
Please register or sign in to comment