• Home
Name Date Size #Lines LOC

..--

brillo/04-Jul-2025-45,33331,519

install_attributes/04-Jul-2025-274160

policy/04-Jul-2025-2,5931,788

.clang-formatD04-Jul-20251.2 KiB

Android.bpD04-Jul-20259.4 KiB332306

BUILD.gnD04-Jul-202518.1 KiB670618

METADATAD04-Jul-202539 43

MODULE_LICENSE_BSDD04-Jul-20250

NOTICED04-Jul-20251.5 KiB2827

OWNERSD04-Jul-2025118 32

PRESUBMIT.cfgD04-Jul-2025177 75

README.mdD04-Jul-2025897 2114

libpolicy.verD04-Jul-2025443 2016

testrunner.ccD04-Jul-2025431 178

testrunner_android.ccD04-Jul-2025879 278

README.md

1# libbrillo: platform utility library
2
3libbrillo is a shared library meant to hold common utility code that we deem
4useful for platform projects.
5It supplements the functionality provided by libbase/libchrome since that
6project, by design, only holds functionality that Chromium (the browser) needs.
7As a result, this tends to be more OS-centric code.
8
9## AOSP Usage
10
11This project is also used by [Update Engine] which is maintained in AOSP.
12However, AOSP doesn't use this codebase directly, it maintains its own
13[libbrillo fork](https://android.googlesource.com/platform/external/libbrillo/).
14
15To help keep the projects in sync, we have a gsubtree set up on our GoB:
16https://chromium.googlesource.com/chromiumos/platform2/libbrillo/
17
18This allows AOSP to cherry pick or merge changes directly back into their fork.
19
20[Update Engine]: https://android.googlesource.com/platform/system/update_engine/
21