Ok, I did understand that no APK at all is created by the Project Library, it doesn't even get compiled, it does get compiled when the "host" project is compiled... But I don't get what you mean by "it is to merge stuff into the parent project"... I mean, you have to redeclare all used activities/services/whatever into the "hosts"-project manifest, by referencing the package name of the Project's Library components... Or do you mean something else with "merge stuff" ?
On 5 okt, 17:43, Mark Murphy <mmur...@commonsware.com> wrote: > On Tue, Oct 5, 2010 at 11:30 AM, MobDev <developm...@mobilaria.com> wrote: > > well, actually in a Project Library a Manifest is created as well... > > Don't ask me what for but it's there :P > > It is to merge stuff into the parent project. > > > So there *would* be a place to put it in :P > > No, it is not. The library's manifest is not included in the final > APK, and the version information in the final APK is from the main > project, not the library. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy > > Android Training in London:http://skillsmatter.com/go/os-mobile-server -- 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
