You can't link one .apk to another to directly use its classes. The only option right now is to statically link the code into each app that wants to use it, or to use a lose-coupling mechanism based on activity, receiver, service, and/or provider components.
On Tue, Aug 18, 2009 at 5:43 PM, Chris McCurdy < [email protected]> wrote: > > I'm trying to develop a new app which enhances one of my previous > apps, but still have them be separate packages. The first is required, > and the second is optional. And I want the first to be able to > reference classes from the second. Is there any way to actually do > this? Would the second app have to be distributed as a library instead > of an application? > > > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
