Try Java Build Path > Libraries > Add External Class Folder.
- Juan T. On Jan 20, 12:29 pm, luke <luke.hu...@gmail.com> wrote: > I have two projects that share classes in a third project. Eclipse > happily allows me to reference these external classes when I am > developing the two dependant projects (as long as the Java Build Path > is set up right), but when I try launching the dependant projects, the > external classfiles are not copied into the .apk for some reason, so > at runtime I get unsatisfied link errors. I don't want to have to > maintain multiple copies of the same source file, or even have a copy > of these external classfiles in the dependant projects. I also want > to avoid adding an extra build step where I build the external > classfiles, package them up in a .jar file and include them in the > dependant projects. > > How can I get the Android SDK to simply put a copy of any referenced > (non-SDK, non-project) external classes in the .apk at build time? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
