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

Exempt-From-Owner-Approval: Mechanical change involving a lot of owners.
Change-Id: I3153b62637e09e9720cb47e3e977c79f5e0d972b
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/2492340
Reviewed-by: Jeffrey Kardatzke <jkardatzke@google.com>
Reviewed-by: Clark Chung <ckclark@chromium.org>
Reviewed-by: Joe Tessler <jrt@chromium.org>
Reviewed-by: Chris McDonald <cjmcdonald@chromium.org>
Reviewed-by: Toni Baržić <tbarzic@chromium.org>
Reviewed-by: Tom Hughes <tomhughes@chromium.org>
Reviewed-by: Sergei Datsenko <dats@chromium.org>
Reviewed-by: Xinglong Luan <alanlxl@chromium.org>
Reviewed-by: Tatsuhisa Yamaguchi <yamaguchi@chromium.org>
Reviewed-by: Yoshiki Iguchi <yoshiki@chromium.org>
Reviewed-by: Archie Pusaka <apusaka@chromium.org>
Reviewed-by: Chirantan Ekbote <chirantan@chromium.org>
Reviewed-by: Ryo Hashimoto <hashimoto@chromium.org>
Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org>
Reviewed-by: Eric Caruso <ejcaruso@chromium.org>
Reviewed-by: Hidehiko Abe <hidehiko@chromium.org>
Reviewed-by: Jae Hoon Kim <kimjae@chromium.org>
Commit-Queue: Qijiang Fan <fqj@google.com>
Tested-by: Qijiang Fan <fqj@google.com>
GitOrigin-RevId: b733c2848a803e1b9a6fd4a71cf94edf76e98be5
1 file changed
tree: 5df7c9a9e7c4d0b1db5578acc29eed36efcf7a7f
  1. brillo/
  2. install_attributes/
  3. policy/
  4. BUILD.gn
  5. libpolicy.ver
  6. OWNERS
  7. PRESUBMIT.cfg
  8. README.md
  9. testrunner.cc
README.md

libbrillo: platform utility library

libbrillo is a shared library meant to hold common utility code that we deem useful for platform projects. It supplements the functionality provided by libbase/libchrome since that project, by design, only holds functionality that Chromium (the browser) needs. As a result, this tends to be more OS-centric code.

AOSP Usage

This project is also used by Update Engine which is maintained in AOSP. However, AOSP doesn't use this codebase directly, it maintains its own libbrillo fork.

To help keep the projects in sync, we have a gsubtree set up on our GoB: https://chromium.googlesource.com/chromiumos/platform2/libbrillo/

This allows AOSP to cherry pick or merge changes directly back into their fork.