On Thu, May 14, 2009 at 10:19 AM, Alexey Volovoy <[email protected]> wrote: > > On Apr 28, 12:41 pm, Raphael <[email protected]> wrote: >> Your question isn't quite clear. You might want to rephrase it. >> > How to create to packages from same code base ?
We currently don't have a good story for this especially since, as you found and said in your first post, the R class package depends on the project. One solution is to move android-agnostic code in a separate project building a jar library that you then package in your various android projects. It's not ideal though. >> For your post subject: what identifies an application is the package >> name that you provide in the AndroidManifest.xml. > > I'm very well aware of that . > >> As for Ant, you shouldn't create the project manually. Instead use the >> android tool: > > That just doesn't make any sense. Why i can't create it manually > again ? The ant project uses a sophisticated build.xml file and no offense but you are unlikely to figure it out magically -- looking at an existing one is the best way to understand it. Starting with SDK 1.5_r1, the build.xml actually doesn't contain much anymore. Most of the rules are in the sdk/platform/android-1.N/templates/android_rules.xml. We designed that new structure to make it easier for people to customize the part of their build yet let us update the platform specific rules in later sdk. I strongly suggest you create a skeleton ant project using the "android create project" command-line and look at what has been generated. Then feel free to modify it as you wish. R/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
