no  i do not think that this is the case this is a  cc file and we set brillo in libchrome s android mk we should probably consider defining brillo system wide  though  building libraries with one set of defines and then including their headers with another is generally an awful idea  and build build config h currently checks for brillo as described above  anyone who includes libchrome s headers without setting brillo might have a bad time i d advocate for defining brillo unconditionally in build build config h to avoid this  except that would break chrome os once it is building libchrome from the aosp repository see also the disgusting hacks i added to base  years ago to prevent ndebug mismatches  baseinitloggingimpl built with ndebug and baseinitloggingimpl built without ndebug in logging h eventually resulting in the cros debug eclass  i think 