On Fri, Jul 16, 2010 at 12:01 PM, Mark Carter <[email protected]> wrote: > I'm trying to avoid having to change every import com.mycompany.app1.R > statement in my project. The goal here is to change it in as few places as > possible.
Option #1: Add a step to your build process to remove the final attribute from the generated R class before compilation. Option #2: Add a step to your build process to move the generated R class to the package of your choosing before compilation. Option #3: Modify your build process to supply the -J switch to aapt to control where R gets generated. Option #4: Don't use the R constants directly, but rather look them up via getResources().getIdentifier() or Java reflection at runtime, caching aggressively to minimize performance impacts. Option #5: Work to get the library project going. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Warescription: Three Android Books, Plus Updates, One Low Price! -- 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
