For what it is worth, the 1.5 SDK does move the R.java out into a
different directory (myProject/gen/com.needle.noo), which may solve
one of your problems.

But I don't see how you'd get round having the package name in all the
source files (or, at least, in all the activities & so on) without
introducing a preprocessor.

The new SDK also has something in the Android section of the project
properties called 'Project APK configurations', which is clearly about
some kind of multiple-build-configuration mechanism, but I have not
worked out what it does yet. Perhaps it is the answer to all our hopes
and dreams...

R.


On Apr 21, 9:56 am, Jon Colverson <jjc1...@gmail.com> wrote:
> On Apr 20, 1:23 pm, Mariano Kamp <mariano.k...@gmail.com> wrote:
>
> > But isn't the real problem that you would need a totally different
> > package name to upload it to the Android Market?
>
> I'd love to hear if anyone has an elegant solution for this. Mine is
> very ugly:
>
> I have one manifest file for my full version and one of the demo
> version. The demo manifest has a different package name (just "demo"
> appended to the main package name). When I want to build the demo for
> release I replace the manifest with the demo version and then I have
> to use Eclipse to rename my main Java package to match.
>
> Anyone have a better way? I spent a day trying different ways of doing
> this, with different projects using a common source directory, but the
> insurmountable problem was that the R.java resource file was always
> put in the package matching the manifest's package name.
>
> --
> Jon
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to