So if you have three different projects (each with their own package)
then you have three different generated R files. So the generic
project uses its own R.java and the pro project uses its own R.java
AND the R.java for the generic project.
I'm not sure I understand the problem - maybe because
If someone wants to add an option to aapt to rewrite the .apk to have a
different package name than the one in the manifest, I'd love to review it.
This is a little tricky -- you need to rewrite the manifest's components and
such to also work with the new package -- but should be quite doable.
http://dev.bostone.us/2009/05/02/android-how-to-deploy-multiple-versions-of-the-same-app/
this may help you.
On Sep 3, 4:41 pm, Datoh dato...@gmail.com wrote:
Hi,
I want to use the same eclipse project to maintain only one source
code (or two projects that refer to a generic project).
My
I want to use the same eclipse project to maintain only one source
code (or two projects that refer to a generic project).
My problem is that the names of the package have to be different on
the market (eg: my.android.app.lite and my.android.app.pro).
In my experience, a complete package rename in all your classes is not
necessary. You do need to change the package attribute in the
manifest tag in your manifest file. We use an ant filter to do this
in our build script. In this manifest file, use absolute fully
qualified classnames (not
5 matches
Mail list logo
