You can't create shared libraries like that. You can link your Android's Eclipse project up to 'regular' JARs (Project build path). When deploying, the classes in these jars will be 'dalviked' and these classes will be deployed with your app on the phone.
You can link your Android's Eclipse project to another Android's Eclipse project. If you deploy the first one, the other one is deployed automatically (when using Eclipse). However, you can't create (shared) jars out of Android Eclipse projects. On Jun 21, 3:35 pm, Paul Turchenko <[email protected]> wrote: > Hi there. I have exactly the same problem. I've tried to ask silimar > question here about a month ago, but noone managed to give me a proper > answer. It seems like google restricts programmers from creating their > own android libraries. > > On Jun 20, 10:19 am, "[email protected]" > > > > <[email protected]> wrote: > > Hi, > > > I've factored out some common code into an Android project, which > > (certainly under Eclipse) is required to have an AndroidManifest.xml. > > > If I export this shared code as a jarfile and link it to my main > > project, the Davik compiler gives an error about a duplicate manifest. > > If I don't include the mainifest, Davik gives an error that the > > manifest is missing. > > > Any helpful suggestions would be appreciated. > > > Nick.- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
