You will have to use Android library projects instead of simply referring to the other project in Eclipse. That will create the R class to both projects. Follow instructions here: http://developer.android.com/guide/developing/eclipse-adt.html#libraryProject to get it going.
On Aug 26, 4:39 pm, Warren <[email protected]> wrote: > I have ten, possibly more, apps I'm developing that all share logic. > 50-75% of the logic is the same - perfect for some time of library or > code sharing. However, after reading the posts here and trying to > share code in Eclipse, I'm not sure that's going to work. I tried > going to project -> properties -> build path -> link source and adding > the src and gen folders of the project with the shared code and then > importing the classes I need. That seems to work in the IDE, but gives > an error during runtime: class not found. This seems to be a common > error for people attempting this. > > I am slowly deciding that shared code is not the best approach in this > scenario. Android doesn't seem to work well with this type of code > sharing. For one thing resources are not packed in libraries, but > references (R.whatever) must exist so as not to create errors. This > can be designed around, but the effort and headache is probably worse > than simply creating multiple copies. > > What are you thoughts on the topic? My experience seems typical, > based on what I've read. Is it? Have you experienced success or > failure with sharing code and/or custom libraries? Am I off-base in > thinking that multiple code copies will be smoother sailing than > fighting the shared code approach? -- 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
