On Jul 6, 7:06 pm, Mark Murphy <[email protected]> wrote: > 2011/7/6 Kostya Vasilyev <[email protected]>: > > > 06.07.2011 20:31, Guillaume пишет: > > >> if com.lib is the > >> lib package, I should be able to access com.lib.R from the > >> application > > > Maybe it's just me, but I wouldn't call this a typical usage pattern. The > > way I do it, the library resources are accessed by the library code, and > > application resources - by the application code. > > > The R.java merging is a build system implementation detail, and doesn't > > interfere with this (typical, to me) usage. > > That's certainly the way I approach it. The library is self contained > and cannot access application-supplied resources, short of reflection > or passing in resource IDs. You're right and I don't want to access lib resources from application or vice versa. But in my case the lib just can't get compiled in the application as it cannot access its own resources. I'm sure that my manifests are correct.
> > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy > > Android App Developer Books:http://commonsware.com/books -- 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
