each library has own unique package name. You have to set it separate from other library and application.
If library is com.example.lib and app is com.example.app you can't do com.example.app.R in the com.example.lib, it need to be separate. On Thursday, June 13, 2013 9:18:45 PM UTC-4, Nathan wrote: > > Yes, I have attempted to Google this problem. I found unhelpful and > conflicting advice. > > After updating to > ADT 22, > SDK Tools 22 > Built Tools 17 > Platform Tools 17 > > Which were all sort of a package deal. > > I can't build a project that depends on a library project. > > I've try dropping and re adding it, of course. > > The jar file of the library project shows up as an Android Dependency in > the dependent project. All that looks correct. > > But noone has told the compiler that. It fails to resolve package names > which are clearly in the library project. > > Now I remember why I don't rush to download all these updates. :( > > Nathan > -- -- 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 --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
