BTW, my Android.mk is: ######################################################## LOCAL_PATH := $(call my-dir) include $(CLEAR_VARS)
LOCAL_MODULE_TAGS := user development LOCAL_STATIC_JAVA_LIBRARIES := servletlib LOCAL_SRC_FILES := $(call all-subdir-java-files) LOCAL_PACKAGE_NAME := MyApp include $(BUILD_PACKAGE) include $(CLEAR_VARS) LOCAL_PREBUILT_STATIC_JAVA_LIBRARIES := servletlib:lib/servlet- api-2.5-20081211.jar.jar include $(BUILD_MULTI_PREBUILT) # Use the folloing include to make our test apk. include $(call all-makefiles-under,$(LOCAL_PATH)) ######################################################## On Dec 2, 3:45 pm, nowingfly <[email protected]> wrote: > Hi All, > I have an app with some 3rd-party jar references. When building in > Eclipse, those .properties files in the jars are included in the > generated apk with the help of ADT plugins. And the structure of the > apk would look like as below: > | > |---javax > | |---servlet > | |---LocalStrings.properties > | ... > |---res > |---AndroidManifest.xml > |---resources.arsc > |---classes.dex > > But if putting it in Android source code and building with Android.mk > in Linux, these .properties files are not extracted and included in > the generated apk which will cause some classes initialization error. > The structure of the apk might only look like: > | > |---res > |---AndroidManifest.xml > |---resources.arsc > |---classes.dex > > Could anybody tell me how to make the Android.mk generate equivalent > apk as ADT does? > Thansk in advance! > > BRs > Chaohong -- You received this message because you are subscribed to the Google Groups "Android Developers" group. 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-developers?hl=en
