commit | 237ad18a293565c92acfbb1f9170bab7714eef35 | [log] [tgz] |
---|---|---|
author | Qijiang Fan <fqj@chromium.org> | Wed Oct 28 09:41:55 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Oct 29 15:17:14 2020 |
tree | aa5c80eca011d83e5c8532f991e61d6211be68e6 | |
parent | a20cb69485d3a117e6b46aa736bb5b6d1256ffcf [diff] |
sis-updater: 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: Ibe1b00a011a7852c732a9b42581ba7fc769ff5f1 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/sis-updater/+/2505270 Reviewed-by: Joe Tessler <jrt@chromium.org> Commit-Queue: Qijiang Fan <fqj@google.com> Tested-by: Qijiang Fan <fqj@google.com>
The code was proviced by SiS and modified by Google. Modifications include:
On Linux, should run as root.
At the root of the repository: make
.
Under Chrome OS development enviroment: emerge-${BOARD} sis-updater
.
Just run ./sis-updater
.