libbrillo: Remove base::MessageLoop::current()

base::MessageLoop::current() will be deprecated in libchrome r680000.
Check if current thread is running a message loop by
base::MessageLoopCurrent::IsSet().
base::MessageLoop::current()->task_runner() is replaced by equivalent
base::ThreadTaskRunnerHandle::Get().

BUG=chromium:1054279
TEST=unittests

Change-Id: Ibafe5df63362c8b6f77f2cb06170a6dcac718731
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/2148693
Tested-by: Grace Cham <hscham@chromium.org>
Reviewed-by: Qijiang Fan <fqj@google.com>
Reviewed-by: Hidehiko Abe <hidehiko@chromium.org>
Commit-Queue: Grace Cham <hscham@chromium.org>
Cr-Mirrored-From: https://chromium.googlesource.com/chromiumos/platform2
Cr-Mirrored-Commit: 4a9b42d2b51a1f2395f64fdc7bc646af8c65ded2
2 files changed
tree: 5c7cf64223de8786cff9412c692b3bfd6b48257f
  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.