Add one android project as a library in AOSP App

Question

I want to add some features into Browser app by start an activity from another android application. It gives me `package does not exist` while I make the Main Project. Notice that I see the AndroidLib is built successfully into an `out/target/product/generic/data/app/AndroidLib.apk` Here are two android.mk files: AndroidLib(a normal Android App) ``` LOCAL_PATH:= $(call my-dir) include $(CLEAR_VARS) LOCAL_STATIC_JAVA_LIBRARIES := \ google-ps \ android-support-v4 \ LOCAL_SRC_FILES := \ $(call all-java-files-under, src) \ LOCAL_MODULE := AndroidLib LOCAL_PACKAGE_NAME := AndroidLib LOCAL_MODULE_TAGS := tests LOCAL_PREBUILT_STATIC_JAVA_LIBRARIES := google-ps:libs/google-play-services.jar include $(BUILD_PACKAGE) # additionally, build tests in sub-folders in a separate .apk include $(call all-makefiles-under,$(LOCAL_PATH)) ``` Browser App ``` LOCAL_PATH:= $(call my-dir) include $(CLEAR_VARS) LOCAL_MODULE_TAGS := optional LOCAL_STATIC_JAVA_LIBRARIES := \ android-common \ guava \ android-supp…

Accepted Answer

Update Essentially your problem is that the line: ``` LOCAL_REQUIRED_MODULES := SoundRecorder, AndroidLib ``` Tells the Android build that your Browser depends on `AndroidLib` being built first, however it will not be linked to `AndroidLib` in any way. To do that you need: ``` LOCAL_JAVA_LIBRARIES := AndroidLib ``` Except that requires the `AndroidLib` to be a java library project, using the build type: ``` include $(BUILD_JAVA_LIBRARY) ``` And java libraries cannot include resources, unfortunately. And there is no way to link one app to another app in the Android build system. We are working around that issue frequently, and it is frankly a bit of a mess to do so. But the only workaround we have found is to include all the resources directly in the apps that use those resources. Sorry. How to make your `AndroidLib` a java library and link to it Your android lib should probably be built as a java library, and not as a app package. So instead of: ``` include $(BUILD_PACKAGE) ``` You should probably do: ``` include $(BUILD_JAVA_LIBRARY) ``` Then you lib will be placed in `out/target/product/generic/system/framework/AndroidLib.jar` along with the other system libs. Also you do not need a `LOCAL_MODULE_NAME` for a lib, it is only applicable for an app. So strip that. And you should probably consider changing your `LOCAL_MODULE_TAGS` to: ``` LOCAL_MODULE_TAGS := user ``` `tests` indicates that you lib should only be built for testing, `user` says to build you lib for all user builds (and implicitly also for engineering builds) In you app `Android.mk` you should then add a line: ``` LOCAL_JAVA_LIBRARIES := AndroidLib ``` Such that your app will be built with `AndroidLib` in the classpath. In you apps `AndroidManifest.xml` you also need to put a uses library in the `application` tag: ``` ``` And last you need to create a permissions xml file, with the following content: ``` ``` And update your product configuration file such that the xml file will be deployed to target: ``` PRODUCT_COPY_FILES += device/XXX/libs/AndroidLib.xml:system/etc/permissions/AndroidLib.xml ``` Replace `device/XXX/libs/` with the path to the permissions xml file. This is how we add and use an Android library in our Android builds. I hope it helps. :)

Add one android project as a library in AOSP App

Solution

Problem