Google Git
Sign in
android/platform/external/libbrillo/refs/heads/android17-release
commit
eae502014c9048318fc1c072e66924bcd88267d6
[log]
author
Android Build Coastguard Worker <android-build-coastguard-worker@google.com>
Wed Dec 17 18:18:15 2025 -0800
committer
Android Build Coastguard Worker <android-build-coastguard-worker@google.com>
Wed Dec 17 18:18:15 2025 -0800
tree
50395bf96a86647ea1d6bac63292d3cddff60b39
parent
7244f3b1684c280fd799e96a83f0a43bd122138e [diff]
parent
a0f718a7b9c0d17f08d3cb235dc4b92e03c1b0bb [diff]
Snap for 14611006 from a0f718a7b9c0d17f08d3cb235dc4b92e03c1b0bb to 26Q2-release

Change-Id: If319dab6b7e341ea2c514a0b5f56294be91c3c59
tree: 50395bf96a86647ea1d6bac63292d3cddff60b39
  1. brillo/
  2. install_attributes/
  3. policy/
  4. .clang-format ⇨ ../../build/tools/brillo-clang-format
  5. Android.bp
  6. BUILD.gn
  7. libpolicy.ver
  8. METADATA
  9. MODULE_LICENSE_BSD
  10. NOTICE
  11. OWNERS
  12. PRESUBMIT.cfg
  13. README.md
  14. testrunner.cc
  15. testrunner_android.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.