Thanks a lot Dan for your reply. Here is my question to Google, why you
break the backward compatibility like that. Would it be much better to let
the "Android.bp" recognize the library or entity exported from Android.mk.
There are hundreds of Android,mk files still exist in AOSP source tree
All dependencies of an Android.bp file must be in Android.bp, not
Android.mk. So you'll need to convert your libmine description to an
Android.bp file.
- Dan
On Wed, Sep 18, 2019 at 1:51 PM Jack Rong wrote:
> I have a scenario that is to link in a Java static library built from an
> Android.mk
You'll need to execute conan before running the android build. It's not
enforced yet, but the source tree is expected to be read-only during the
build -- in particularly we start caching the Android.bp files nearly
immediately upon build startup, so adding new ones isn't going to work.
Nothing
hello,
I build AOSP as https://source.android.com/devices/tech/debug/hwasan
required, patched kernel with
https://lore.kernel.org/patchwork/project/lkml/list/?series=375855=both
, build kernel, build AOSP with new kernel.
but after flush and reboot, pixel 2 stuck at show "Android" picture,
