That generally should be an error, as we normally require modules to be unique based on the combination of LOCAL_MODULE / LOCAL_IS_HOST_MODULE / LOCAL_MODULE_CLASS (this is in build/make/core/base_rules.mk <https://cs.android.com/android/platform/superproject/+/master:build/make/core/base_rules.mk;drc=fca369e4e3694b0f549613362f056ffff8c88f67;l=322> )
If that isn't triggering, you may be making two rules to create the same /system/frameworks/X.jar, and you should be getting a warning like this: build/make/core/....mk:LLL: warning: overriding commands for target `out/target/product/mydevice/system/frameworks/X.jar' build/make/core/...mk:LLL: warning: ignoring old commands for target `out/target/product/mydevice/system/frameworks/X.jar' That should be an error by default unless you've got BUILD_BROKEN_DUP_RULES set (at least as of Android-Q iirc). That means you're getting one of the two, or sometimes a mix, but we don't really even guarantee which one you'll get (it's fairly stable, but can change based on ordering/etc). What did you intend for the snippet to do? How would we install both classes.jar and classes-header.jar onto the device? Same filenames? Different filenames? Why do they share the same module name? - Dan On Tue, Apr 14, 2020 at 8:10 AM Pranitha Reddy < [email protected]> wrote: > Hello > Say there is module 'X' writtern twice in Android.mk > > include $(CLEAR_VARS) > LOCAL_MODULE := X > LOCAL_MODULE_CLASS := JAVA_LIBRARIES > LOCAL_SRC_FILES := same_path/classes-header.jar > > > > include $(CLEAR_VARS) > LOCAL_MODULE := X > LOCAL_MODULE_CLASS := JAVA_LIBRARIES > LOCAL_SRC_FILES := same_path/classes.jar > > Is there any way to install X such that both classes.jar and > classes-header.jar will be in out folder? > At present with above Android.mk, the rule that is writtern first is being > compiled and the rest is being ingnored and so Im seeing only > classes-header.jar in out folder > > Thanks in advance > > -- > -- > 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/CAH4VoYmaY%3DokDbzrBCa%2BGt9ysJNLasKMeK2NKVTH2Lq95QjE3w%40mail.gmail.com > <https://groups.google.com/d/msgid/android-building/CAH4VoYmaY%3DokDbzrBCa%2BGt9ysJNLasKMeK2NKVTH2Lq95QjE3w%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- -- 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/CALQgHdnpF2%2BgT_C9wymuA3VtCDEjP3g4uy4SAXyZ04%3DVEEEOcw%40mail.gmail.com.
