Hi, I found this change which I believe answers my question: https://cs.android.com/android/_/android/platform/frameworks/base/+/b896c588af5489999c3a22e3713a2491811456c2
"... building all of CarSystemUI as a library and then including that library as a static lib for an android_app target. Thus anyone that wants to build a derivative to CarSystemUI can include that library and start extending. It is the same mechanism that allows CarSystemUI to extend the phone SystemUI" I hope this saves time to others. On Thursday, August 13, 2020 at 8:26:27 PM UTC+2 [email protected] wrote: > Hi, > > I have a doubt regarding the new CarSystemUI introduced in Android Q. In > Android P, most of the code and resources from CarSystemUI were part of the > original SystemUI, so in order to build a custom SystemUI one would just > need to override the original SystemUI. In Q, however, CarSystemUI is > already overriding the original SystemUI. My question is what is the > approach to follow in Q in order to build a custom car SystemUI, should > this custom one replace CarSystemUI or still SystemUI? I have been > struggling with this for a while due to some dependencies in the .bp files > and I am not sure which approach is the right one. > > Thanks a lot for your help! > -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/f931c897-fc52-493d-ab2f-e85074e83f91n%40googlegroups.com.
