resources/*.dtd in MANIFEST.MF


Last Updated:

  1. isup

    isup Member This Topic's Starter

    Joined:
    Jul 9, 2009
    Messages:
    20
    Likes Received:
    0
    My application is built in a Linux system for Andriod. There is a pre-built jar file in the source code, which is static linked to the application. The APK is generated, and the classes in the jar are included in classes.dex too. However, all of resources/*.dtd, resources/*.xsd, *.properties in the jar are not added to the MANIFEST.MF of the generated APK file. However, they are in the MANIFEST.MF file if the application is built by Eclipse. What is wrong in the Linux build?

    Here is the Andriod.mk I used.

    LOCAL_PATH:= $(call my-dir)
    include $(CLEAR_VARS)
    LOCAL_STATIC_JAVA_LIBRARIES := libabc
    LOCAL_MODULE_TAGS := eng development
    LOCAL_SRC_FILES := $(call all-subdir-java-files)
    LOCAL_PACKAGE_NAME := ABC_app
    include $(BUILD_PACKAGE)
    ###############################
    include $(CLEAR_VARS)
    LOCAL_PREBUILT_STATIC_JAVA_LIBRARIES := libabc:lib/Third_party_2.5.jar
    include $(BUILD_MULTI_PREBUILT)
    # Use the folloing include to make our test apk.
    include $(call all-makefiles-under,$(LOCAL_PATH))
     

    Advertisement

Share This Page

Loading...