• Home
Name Date Size #Lines LOC

..--

brillo/03-May-2024-45,30431,497

install_attributes/03-May-2024-274160

policy/03-May-2024-2,5931,788

.clang-formatD03-May-20241.2 KiB

Android.bpD03-May-20249.3 KiB330304

BUILD.gnD03-May-202418.1 KiB670618

METADATAD03-May-202439 43

MODULE_LICENSE_BSDD03-May-20240

NOTICED03-May-20241.5 KiB2827

OWNERSD03-May-2024124 107

PRESUBMIT.cfgD03-May-2024177 75

README.mdD03-May-2024897 2114

libpolicy.verD03-May-2024443 2016

testrunner.ccD03-May-2024431 178

testrunner_android.ccD03-May-2024879 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