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
I have a scenario that is to link in a Java static library built from an
Android.mk file to complete the whole AOSP image build in Android P. The
build system somehow is not versatile enough to discover the static library
built from other project using the Android.mk. Here is an example:
1)
