On Mon, Jul 12, 2010 at 2:16 AM, deg <[email protected]> wrote: > 1) With both projects open in Eclipse, sometimes I make a change to > source in the library and rebuild. The .class file gets rebuilt in the > library project's bin directory, but not in the bin directory of the > main app. This problem persists across multiple builds, and is only > fixed when I hit it with a heavy sledgehammer -- cleaning all, or > breaking and redoing the library dependency. Once fixed, it behaves > ok, at least for many hours.
This is a refresh issue. Eclipse doesn't realize that the source in the library and the main project are the same (because linked folder could link to anything), so editing the library source is considered an external modifications for the version in the main project. The fix is not to clean the projects but to refresh them. The best fix is to set your workspace to automatically refresh (in preferences under General > Workspace). > 2) The key reason I've divided the project into a library and main app > is that we need to ship the library portion to 3rd-party developers. > But, it looks like there is no way to ship an Android library, except > as as source files. How can we ship an Android component to other > developers in a binary form? (Source shipments are unacceptable, > because of management security concerns). This is not possible at the moment. The reason libraries are handled at the source level is that the R class in the library must be created with all the resources (of the main project + all libraries). Xav -- Xavier Ducrohet Android SDK Tech Lead Google Inc. Please do not send me questions directly. Thanks! -- 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
