diff options
| author | Qijiang Fan <fqj@chromium.org> | 2020-10-27 16:31:39 +0900 |
|---|---|---|
| committer | Commit Bot <commit-bot@chromium.org> | 2020-10-28 04:35:55 +0000 |
| commit | b78e1bceba7a70d4ce38452547b123650d18484b (patch) | |
| tree | dcd7af6e7c46dbde078e611171a4b8ef513248da /payload_generator/blob_file_writer_unittest.cc | |
| parent | b0b6cc2b0cfe7a5313b1b416424409be6ea05eb0 (diff) | |
update_engine: use unversioned libchrome libraray.
Libchrome is changing pkg-config and .so library name from
xxxx-${libbase_ver}.{pc,so} to xxx.{pc,so}.
Libchrome uprev rebuild will be handled by ebuild subslot change. And
there's no need to install multiple libchrome. Keeping libbase_ver
suffix will cause troubles on linking libraries when developers wants to
test locally emerge a-single-package without build_packages, after a
libchrome uprev. Especially in a case a package depends on another
package(library), and both depends on libchrome. Thus, removing
libbase_ver from suffix.
BUG=chromium:920513
TEST=CQ
Change-Id: I65cff884c1f852f51b2a7e2dfc258cac340b2747
Reviewed-on: https://chromium-review.googlesource.com/c/aosp/platform/system/update_engine/+/2500818
Reviewed-by: Amin Hassani <ahassani@chromium.org>
Commit-Queue: Qijiang Fan <fqj@google.com>
Tested-by: Qijiang Fan <fqj@google.com>
Diffstat (limited to 'payload_generator/blob_file_writer_unittest.cc')
0 files changed, 0 insertions, 0 deletions