libbrillo: Use std::to_underlying instead of base::to_underlying

Replace base::to_underlying with std::to_underlying in libbrillo. The
platform2 toolchain now supports C++23.

BUG=b:470854927
TEST=CQ

Cq-Depend: chromium:7741160
Change-Id: I7c1c552d8e6989691f07619eae09802b8c8cebde
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/7742400
Reviewed-by: Sarthak Kukreti <sarthakkukreti@google.com>
Commit-Queue: Di Wu <diwux@google.com>
Tested-by: Di Wu <diwux@google.com>
NOKEYCHECK=True
GitOrigin-RevId: ef6bed77c64ab66d0b1c2cfeaf1a749b3610ac0c
1 file changed
tree: bf7ab5e5d432c9f3fde7b87e2ef6f337011f887e
  1. brillo/
  2. install_attributes/
  3. policy/
  4. testdata/
  5. BUILD.gn
  6. libpolicy.ver
  7. OWNERS
  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.