[android-developers] Re: creating a shared jar library
I've sufficiently understood about the reason not to support third party libraries. Goolgle apis as regular sharing libraries can add on %ANDROID_HOME%/ add-on and then Android Applications can use that libraries. Like this, could I add my sharing library on %ANDROID_HOME%/add-on directory? If I can't use the way, how can I share my library? Actually, I'd like to add my library on framework directory and then edit platform.xml to use my library as a sharing library, but because I just use Android Application Framework API, to make my library, I thought I don't need to add my library on framework On 8월27일, 오후2시31분, Dianne Hackborn wrote: > If you are creating your own device, you can have your own shared libraries > that are separate from the framework. We don't support third party shared > libraries mostly because we really don't want to get into dll hell and > library versioning and such at this point. > > 2009/8/26 Mac > > > > > > > > > Thanks, Dianne Hackborn. > > > Could I think the reason that can't support sharing third party > > libraries is that all applications are on each Dalvik VM? > > > And there's any way to share a regular library(.jar) without putting > > the library on application framework layer? > > > On 8월27일, 오후12시17분, Dianne Hackborn wrote: > > > I meant "regular" as what we generally call a shared library in any OS. > > > > A third party shared library is specifically talking about the > > (theoretical > > > not currently possible) case of putting a shared library as an .apk up on > > > market that could be installed by the system and used by other > > applications. > > > > 2009/8/26 Mac > > > > > Hello, Dianne Hackborn. > > > > > I've read all of these mails and I understood most of them. > > > > > But, I don't know one important point of these mails. > > > > > I wonder what the difference of regular shared libraries and third > > > > party shared libraries. > > > > > Could you tell me the difference for me? > > > > > On 8월5일, 오후11시18분, Dianne Hackborn wrote: > > > > > Yes, it is just a regular shared library. > > > > > > On Wed, Aug 5, 2009 at 7:03 AM, GiladH wrote: > > > > > > > Dianne/anyone, > > > > > > > i would like to elaborate on the shared jar's memory model. > > > > > > my understanding is that: > > > > > > > a. the code (read only) segment of the shared jar resides in > > common > > > > > > memory => code will be loaded once regardless of the number of > > > > > > apps > > > > > > using the shared jar > > > > > > b. the data (read/write) segment of the shared jar is part of the > > > > > > calling > > > > > > process'es address space => all static data (blocks, > > constructors > > > > > > etc.) > > > > > > will be initialized _separately_ for each app using the shared > > > > > > jar > > > > > > > are my assumptions correct? > > > > > > > GiladH > > > > > > > On Jul 30, 7:31 pm, Dianne Hackborn wrote: > > > > > > > That only applies if you are making your own device. > > > > > > > > On Thu, Jul 30, 2009 at 8:20 AM, GiladH > > wrote: > > > > > > > > > tnx Dianne. > > > > > > > > after my post i have learned about the ability to 'inject' my > > > > shared > > > > > > > > library into open source Andro, as described in: > > > > >http://android.git.kernel.org/?p=platform/development.git;a=blob;f=sa. > > > > > > .. > > > > > > > > > i take it this option still stands (again - only for open > > source > > > > > > > > platform), right? > > > > > > > > > GiladH > > > > > > > > > On Jul 30, 5:04 pm, Dianne Hackborn > > wrote: > > > > > > > > > Sorry, Android currently doesn't support third party shared > > > > > > libraries. > > > > > > > > > > On Thu, Jul 30, 2009 at 4:13 AM, GiladH > > > > wrote: > > > > > > > > > > > hey, > > > > > > > > > > > i have several apps (each in its own apk, process etc) > > running > > > > at > > > > > > the > > > > > > > > > > same time on user's device. > > > > > > > > > > > these apps are all linked to a single common jar file > > > > (internally > > > > > > > > > > devloped) which contains a large portion of their overall > > code > > > > > > size. > > > > > > > > > > > is there a way for me to force Andro to make this common > > jar > > > > load > > > > > > only > > > > > > > > > > once (e.g. into shared memory)? > > > > > > > > > > > the reason we want to do it this way, btw, are to reduction > > of > > > > each > > > > > > of > > > > > > > > > > the > > > > > > > > > > single apps memory intake, on disk footprint and possibly > > of > > > > their > > > > > > > > > > startup time. > > > > > > > > > > > your help will be appreciated. > > > > > > > > > > > tnx, GilkadH > > > > > > > > > > -- > > > > > > > > > Dianne Hackborn > > > > > > > > > Android framework engineer > > > > > > > > > hack...@android.com > > > > > > > > > > Note: please don't send private questions to me, as I don't > > have > > > > time > > > > > > to > > > > > > > > > provide private support, and so won't reply to such e-mails. > > All
[android-developers] Re: creating a shared jar library
If you are creating your own device, you can have your own shared libraries that are separate from the framework. We don't support third party shared libraries mostly because we really don't want to get into dll hell and library versioning and such at this point. 2009/8/26 Mac > > Thanks, Dianne Hackborn. > > Could I think the reason that can't support sharing third party > libraries is that all applications are on each Dalvik VM? > > And there's any way to share a regular library(.jar) without putting > the library on application framework layer? > > > > On 8월27일, 오후12시17분, Dianne Hackborn wrote: > > I meant "regular" as what we generally call a shared library in any OS. > > > > A third party shared library is specifically talking about the > (theoretical > > not currently possible) case of putting a shared library as an .apk up on > > market that could be installed by the system and used by other > applications. > > > > 2009/8/26 Mac > > > > > > > > > > > > > > > > > Hello, Dianne Hackborn. > > > > > I've read all of these mails and I understood most of them. > > > > > But, I don't know one important point of these mails. > > > > > I wonder what the difference of regular shared libraries and third > > > party shared libraries. > > > > > Could you tell me the difference for me? > > > > > On 8월5일, 오후11시18분, Dianne Hackborn wrote: > > > > Yes, it is just a regular shared library. > > > > > > On Wed, Aug 5, 2009 at 7:03 AM, GiladH wrote: > > > > > > > Dianne/anyone, > > > > > > > i would like to elaborate on the shared jar's memory model. > > > > > my understanding is that: > > > > > > > a. the code (read only) segment of the shared jar resides in > common > > > > > memory => code will be loaded once regardless of the number of > > > > > apps > > > > > using the shared jar > > > > > b. the data (read/write) segment of the shared jar is part of the > > > > > calling > > > > > process'es address space => all static data (blocks, > constructors > > > > > etc.) > > > > > will be initialized _separately_ for each app using the shared > > > > > jar > > > > > > > are my assumptions correct? > > > > > > > GiladH > > > > > > > On Jul 30, 7:31 pm, Dianne Hackborn wrote: > > > > > > That only applies if you are making your own device. > > > > > > > > On Thu, Jul 30, 2009 at 8:20 AM, GiladH > wrote: > > > > > > > > > tnx Dianne. > > > > > > > after my post i have learned about the ability to 'inject' my > > > shared > > > > > > > library into open source Andro, as described in: > > > > >http://android.git.kernel.org/?p=platform/development.git;a=blob;f=sa. > > > > > .. > > > > > > > > > i take it this option still stands (again - only for open > source > > > > > > > platform), right? > > > > > > > > > GiladH > > > > > > > > > On Jul 30, 5:04 pm, Dianne Hackborn > wrote: > > > > > > > > Sorry, Android currently doesn't support third party shared > > > > > libraries. > > > > > > > > > > On Thu, Jul 30, 2009 at 4:13 AM, GiladH > > > wrote: > > > > > > > > > > > hey, > > > > > > > > > > > i have several apps (each in its own apk, process etc) > running > > > at > > > > > the > > > > > > > > > same time on user's device. > > > > > > > > > > > these apps are all linked to a single common jar file > > > (internally > > > > > > > > > devloped) which contains a large portion of their overall > code > > > > > size. > > > > > > > > > > > is there a way for me to force Andro to make this common > jar > > > load > > > > > only > > > > > > > > > once (e.g. into shared memory)? > > > > > > > > > > > the reason we want to do it this way, btw, are to reduction > of > > > each > > > > > of > > > > > > > > > the > > > > > > > > > single apps memory intake, on disk footprint and possibly > of > > > their > > > > > > > > > startup time. > > > > > > > > > > > your help will be appreciated. > > > > > > > > > > > tnx, GilkadH > > > > > > > > > > -- > > > > > > > > Dianne Hackborn > > > > > > > > Android framework engineer > > > > > > > > hack...@android.com > > > > > > > > > > Note: please don't send private questions to me, as I don't > have > > > time > > > > > to > > > > > > > > provide private support, and so won't reply to such e-mails. > All > > > > > such > > > > > > > > questions should be posted on public forums, where I and > others > > > can > > > > > see > > > > > > > and > > > > > > > > answer them. > > > > > > > > -- > > > > > > Dianne Hackborn > > > > > > Android framework engineer > > > > > > hack...@android.com > > > > > > > > Note: please don't send private questions to me, as I don't have > time > > > to > > > > > > provide private support, and so won't reply to such e-mails. All > > > such > > > > > > questions should be posted on public forums, where I and others > can > > > see > > > > > and > > > > > > answer them. > > > > > > -- > > > > Dianne Hackborn > > > > Android framework engineer > > > > hack...@android.com > > > > > > Note: please don't send private questions to me, as I don't
[android-developers] Re: creating a shared jar library
Thanks, Dianne Hackborn. Could I think the reason that can't support sharing third party libraries is that all applications are on each Dalvik VM? And there's any way to share a regular library(.jar) without putting the library on application framework layer? On 8월27일, 오후12시17분, Dianne Hackborn wrote: > I meant "regular" as what we generally call a shared library in any OS. > > A third party shared library is specifically talking about the (theoretical > not currently possible) case of putting a shared library as an .apk up on > market that could be installed by the system and used by other applications. > > 2009/8/26 Mac > > > > > > > > > Hello, Dianne Hackborn. > > > I've read all of these mails and I understood most of them. > > > But, I don't know one important point of these mails. > > > I wonder what the difference of regular shared libraries and third > > party shared libraries. > > > Could you tell me the difference for me? > > > On 8월5일, 오후11시18분, Dianne Hackborn wrote: > > > Yes, it is just a regular shared library. > > > > On Wed, Aug 5, 2009 at 7:03 AM, GiladH wrote: > > > > > Dianne/anyone, > > > > > i would like to elaborate on the shared jar's memory model. > > > > my understanding is that: > > > > > a. the code (read only) segment of the shared jar resides in common > > > > memory => code will be loaded once regardless of the number of > > > > apps > > > > using the shared jar > > > > b. the data (read/write) segment of the shared jar is part of the > > > > calling > > > > process'es address space => all static data (blocks, constructors > > > > etc.) > > > > will be initialized _separately_ for each app using the shared > > > > jar > > > > > are my assumptions correct? > > > > > GiladH > > > > > On Jul 30, 7:31 pm, Dianne Hackborn wrote: > > > > > That only applies if you are making your own device. > > > > > > On Thu, Jul 30, 2009 at 8:20 AM, GiladH wrote: > > > > > > > tnx Dianne. > > > > > > after my post i have learned about the ability to 'inject' my > > shared > > > > > > library into open source Andro, as described in: > > >http://android.git.kernel.org/?p=platform/development.git;a=blob;f=sa. > > > > .. > > > > > > > i take it this option still stands (again - only for open source > > > > > > platform), right? > > > > > > > GiladH > > > > > > > On Jul 30, 5:04 pm, Dianne Hackborn wrote: > > > > > > > Sorry, Android currently doesn't support third party shared > > > > libraries. > > > > > > > > On Thu, Jul 30, 2009 at 4:13 AM, GiladH > > wrote: > > > > > > > > > hey, > > > > > > > > > i have several apps (each in its own apk, process etc) running > > at > > > > the > > > > > > > > same time on user's device. > > > > > > > > > these apps are all linked to a single common jar file > > (internally > > > > > > > > devloped) which contains a large portion of their overall code > > > > size. > > > > > > > > > is there a way for me to force Andro to make this common jar > > load > > > > only > > > > > > > > once (e.g. into shared memory)? > > > > > > > > > the reason we want to do it this way, btw, are to reduction of > > each > > > > of > > > > > > > > the > > > > > > > > single apps memory intake, on disk footprint and possibly of > > their > > > > > > > > startup time. > > > > > > > > > your help will be appreciated. > > > > > > > > > tnx, GilkadH > > > > > > > > -- > > > > > > > Dianne Hackborn > > > > > > > Android framework engineer > > > > > > > hack...@android.com > > > > > > > > Note: please don't send private questions to me, as I don't have > > time > > > > to > > > > > > > provide private support, and so won't reply to such e-mails. All > > > > such > > > > > > > questions should be posted on public forums, where I and others > > can > > > > see > > > > > > and > > > > > > > answer them. > > > > > > -- > > > > > Dianne Hackborn > > > > > Android framework engineer > > > > > hack...@android.com > > > > > > Note: please don't send private questions to me, as I don't have time > > to > > > > > provide private support, and so won't reply to such e-mails. All > > such > > > > > questions should be posted on public forums, where I and others can > > see > > > > and > > > > > answer them. > > > > -- > > > Dianne Hackborn > > > Android framework engineer > > > hack...@android.com > > > > Note: please don't send private questions to me, as I don't have time to > > > provide private support, and so won't reply to such e-mails. All such > > > questions should be posted on public forums, where I and others can see > > and > > > answer them. > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. --~--~-~--~~~---~--~~ You received this message because you are subs
[android-developers] Re: creating a shared jar library
I meant "regular" as what we generally call a shared library in any OS. A third party shared library is specifically talking about the (theoretical not currently possible) case of putting a shared library as an .apk up on market that could be installed by the system and used by other applications. 2009/8/26 Mac > > Hello, Dianne Hackborn. > > I've read all of these mails and I understood most of them. > > But, I don't know one important point of these mails. > > I wonder what the difference of regular shared libraries and third > party shared libraries. > > Could you tell me the difference for me? > > > On 8월5일, 오후11시18분, Dianne Hackborn wrote: > > Yes, it is just a regular shared library. > > > > > > > > > > > > On Wed, Aug 5, 2009 at 7:03 AM, GiladH wrote: > > > > > Dianne/anyone, > > > > > i would like to elaborate on the shared jar's memory model. > > > my understanding is that: > > > > > a. the code (read only) segment of the shared jar resides in common > > > memory => code will be loaded once regardless of the number of > > > apps > > > using the shared jar > > > b. the data (read/write) segment of the shared jar is part of the > > > calling > > > process'es address space => all static data (blocks, constructors > > > etc.) > > > will be initialized _separately_ for each app using the shared > > > jar > > > > > are my assumptions correct? > > > > > GiladH > > > > > On Jul 30, 7:31 pm, Dianne Hackborn wrote: > > > > That only applies if you are making your own device. > > > > > > On Thu, Jul 30, 2009 at 8:20 AM, GiladH wrote: > > > > > > > tnx Dianne. > > > > > after my post i have learned about the ability to 'inject' my > shared > > > > > library into open source Andro, as described in: > > > > > > > > http://android.git.kernel.org/?p=platform/development.git;a=blob;f=sa. > > > .. > > > > > > > i take it this option still stands (again - only for open source > > > > > platform), right? > > > > > > > GiladH > > > > > > > On Jul 30, 5:04 pm, Dianne Hackborn wrote: > > > > > > Sorry, Android currently doesn't support third party shared > > > libraries. > > > > > > > > On Thu, Jul 30, 2009 at 4:13 AM, GiladH > wrote: > > > > > > > > > hey, > > > > > > > > > i have several apps (each in its own apk, process etc) running > at > > > the > > > > > > > same time on user's device. > > > > > > > > > these apps are all linked to a single common jar file > (internally > > > > > > > devloped) which contains a large portion of their overall code > > > size. > > > > > > > > > is there a way for me to force Andro to make this common jar > load > > > only > > > > > > > once (e.g. into shared memory)? > > > > > > > > > the reason we want to do it this way, btw, are to reduction of > each > > > of > > > > > > > the > > > > > > > single apps memory intake, on disk footprint and possibly of > their > > > > > > > startup time. > > > > > > > > > your help will be appreciated. > > > > > > > > > tnx, GilkadH > > > > > > > > -- > > > > > > Dianne Hackborn > > > > > > Android framework engineer > > > > > > hack...@android.com > > > > > > > > Note: please don't send private questions to me, as I don't have > time > > > to > > > > > > provide private support, and so won't reply to such e-mails. All > > > such > > > > > > questions should be posted on public forums, where I and others > can > > > see > > > > > and > > > > > > answer them. > > > > > > -- > > > > Dianne Hackborn > > > > Android framework engineer > > > > hack...@android.com > > > > > > Note: please don't send private questions to me, as I don't have time > to > > > > provide private support, and so won't reply to such e-mails. All > such > > > > questions should be posted on public forums, where I and others can > see > > > and > > > > answer them. > > > > -- > > Dianne Hackborn > > Android framework engineer > > hack...@android.com > > > > Note: please don't send private questions to me, as I don't have time to > > provide private support, and so won't reply to such e-mails. All such > > questions should be posted on public forums, where I and others can see > and > > answer them. > > > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[android-developers] Re: creating a shared jar library
Hello, Dianne Hackborn. I've read all of these mails and I understood most of them. But, I don't know one important point of these mails. I wonder what the difference of regular shared libraries and third party shared libraries. Could you tell me the difference for me? On 8월5일, 오후11시18분, Dianne Hackborn wrote: > Yes, it is just a regular shared library. > > > > > > On Wed, Aug 5, 2009 at 7:03 AM, GiladH wrote: > > > Dianne/anyone, > > > i would like to elaborate on the shared jar's memory model. > > my understanding is that: > > > a. the code (read only) segment of the shared jar resides in common > > memory => code will be loaded once regardless of the number of > > apps > > using the shared jar > > b. the data (read/write) segment of the shared jar is part of the > > calling > > process'es address space => all static data (blocks, constructors > > etc.) > > will be initialized _separately_ for each app using the shared > > jar > > > are my assumptions correct? > > > GiladH > > > On Jul 30, 7:31 pm, Dianne Hackborn wrote: > > > That only applies if you are making your own device. > > > > On Thu, Jul 30, 2009 at 8:20 AM, GiladH wrote: > > > > > tnx Dianne. > > > > after my post i have learned about the ability to 'inject' my shared > > > > library into open source Andro, as described in: > > > > >http://android.git.kernel.org/?p=platform/development.git;a=blob;f=sa. > > .. > > > > > i take it this option still stands (again - only for open source > > > > platform), right? > > > > > GiladH > > > > > On Jul 30, 5:04 pm, Dianne Hackborn wrote: > > > > > Sorry, Android currently doesn't support third party shared > > libraries. > > > > > > On Thu, Jul 30, 2009 at 4:13 AM, GiladH wrote: > > > > > > > hey, > > > > > > > i have several apps (each in its own apk, process etc) running at > > the > > > > > > same time on user's device. > > > > > > > these apps are all linked to a single common jar file (internally > > > > > > devloped) which contains a large portion of their overall code > > size. > > > > > > > is there a way for me to force Andro to make this common jar load > > only > > > > > > once (e.g. into shared memory)? > > > > > > > the reason we want to do it this way, btw, are to reduction of each > > of > > > > > > the > > > > > > single apps memory intake, on disk footprint and possibly of their > > > > > > startup time. > > > > > > > your help will be appreciated. > > > > > > > tnx, GilkadH > > > > > > -- > > > > > Dianne Hackborn > > > > > Android framework engineer > > > > > hack...@android.com > > > > > > Note: please don't send private questions to me, as I don't have time > > to > > > > > provide private support, and so won't reply to such e-mails. All > > such > > > > > questions should be posted on public forums, where I and others can > > see > > > > and > > > > > answer them. > > > > -- > > > Dianne Hackborn > > > Android framework engineer > > > hack...@android.com > > > > Note: please don't send private questions to me, as I don't have time to > > > provide private support, and so won't reply to such e-mails. All such > > > questions should be posted on public forums, where I and others can see > > and > > > answer them. > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[android-developers] Re: creating a shared jar library
Yes, it is just a regular shared library. On Wed, Aug 5, 2009 at 7:03 AM, GiladH wrote: > > Dianne/anyone, > > i would like to elaborate on the shared jar's memory model. > my understanding is that: > > a. the code (read only) segment of the shared jar resides in common > memory => code will be loaded once regardless of the number of > apps > using the shared jar > b. the data (read/write) segment of the shared jar is part of the > calling > process'es address space => all static data (blocks, constructors > etc.) > will be initialized _separately_ for each app using the shared > jar > > are my assumptions correct? > > GiladH > > > > On Jul 30, 7:31 pm, Dianne Hackborn wrote: > > That only applies if you are making your own device. > > > > > > > > On Thu, Jul 30, 2009 at 8:20 AM, GiladH wrote: > > > > > tnx Dianne. > > > after my post i have learned about the ability to 'inject' my shared > > > library into open source Andro, as described in: > > > > >http://android.git.kernel.org/?p=platform/development.git;a=blob;f=sa. > .. > > > > > i take it this option still stands (again - only for open source > > > platform), right? > > > > > GiladH > > > > > On Jul 30, 5:04 pm, Dianne Hackborn wrote: > > > > Sorry, Android currently doesn't support third party shared > libraries. > > > > > > On Thu, Jul 30, 2009 at 4:13 AM, GiladH wrote: > > > > > > > hey, > > > > > > > i have several apps (each in its own apk, process etc) running at > the > > > > > same time on user's device. > > > > > > > these apps are all linked to a single common jar file (internally > > > > > devloped) which contains a large portion of their overall code > size. > > > > > > > is there a way for me to force Andro to make this common jar load > only > > > > > once (e.g. into shared memory)? > > > > > > > the reason we want to do it this way, btw, are to reduction of each > of > > > > > the > > > > > single apps memory intake, on disk footprint and possibly of their > > > > > startup time. > > > > > > > your help will be appreciated. > > > > > > > tnx, GilkadH > > > > > > -- > > > > Dianne Hackborn > > > > Android framework engineer > > > > hack...@android.com > > > > > > Note: please don't send private questions to me, as I don't have time > to > > > > provide private support, and so won't reply to such e-mails. All > such > > > > questions should be posted on public forums, where I and others can > see > > > and > > > > answer them. > > > > -- > > Dianne Hackborn > > Android framework engineer > > hack...@android.com > > > > Note: please don't send private questions to me, as I don't have time to > > provide private support, and so won't reply to such e-mails. All such > > questions should be posted on public forums, where I and others can see > and > > answer them. > > > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[android-developers] Re: creating a shared jar library
Dianne/anyone, i would like to elaborate on the shared jar's memory model. my understanding is that: a. the code (read only) segment of the shared jar resides in common memory => code will be loaded once regardless of the number of apps using the shared jar b. the data (read/write) segment of the shared jar is part of the calling process'es address space => all static data (blocks, constructors etc.) will be initialized _separately_ for each app using the shared jar are my assumptions correct? GiladH On Jul 30, 7:31 pm, Dianne Hackborn wrote: > That only applies if you are making your own device. > > > > On Thu, Jul 30, 2009 at 8:20 AM, GiladH wrote: > > > tnx Dianne. > > after my post i have learned about the ability to 'inject' my shared > > library into open source Andro, as described in: > > >http://android.git.kernel.org/?p=platform/development.git;a=blob;f=sa... > > > i take it this option still stands (again - only for open source > > platform), right? > > > GiladH > > > On Jul 30, 5:04 pm, Dianne Hackborn wrote: > > > Sorry, Android currently doesn't support third party shared libraries. > > > > On Thu, Jul 30, 2009 at 4:13 AM, GiladH wrote: > > > > > hey, > > > > > i have several apps (each in its own apk, process etc) running at the > > > > same time on user's device. > > > > > these apps are all linked to a single common jar file (internally > > > > devloped) which contains a large portion of their overall code size. > > > > > is there a way for me to force Andro to make this common jar load only > > > > once (e.g. into shared memory)? > > > > > the reason we want to do it this way, btw, are to reduction of each of > > > > the > > > > single apps memory intake, on disk footprint and possibly of their > > > > startup time. > > > > > your help will be appreciated. > > > > > tnx, GilkadH > > > > -- > > > Dianne Hackborn > > > Android framework engineer > > > hack...@android.com > > > > Note: please don't send private questions to me, as I don't have time to > > > provide private support, and so won't reply to such e-mails. All such > > > questions should be posted on public forums, where I and others can see > > and > > > answer them. > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[android-developers] Re: creating a shared jar library
That only applies if you are making your own device. On Thu, Jul 30, 2009 at 8:20 AM, GiladH wrote: > > tnx Dianne. > after my post i have learned about the ability to 'inject' my shared > library into open source Andro, as described in: > > > http://android.git.kernel.org/?p=platform/development.git;a=blob;f=samples/PlatformLibrary/README.txt;h=5ce9d2f7756a0708e9fc0aed7845f3d69d4a6ae0;hb=cupcake > > i take it this option still stands (again - only for open source > platform), right? > > GiladH > > > > > On Jul 30, 5:04 pm, Dianne Hackborn wrote: > > Sorry, Android currently doesn't support third party shared libraries. > > > > > > > > On Thu, Jul 30, 2009 at 4:13 AM, GiladH wrote: > > > > > hey, > > > > > i have several apps (each in its own apk, process etc) running at the > > > same time on user's device. > > > > > these apps are all linked to a single common jar file (internally > > > devloped) which contains a large portion of their overall code size. > > > > > is there a way for me to force Andro to make this common jar load only > > > once (e.g. into shared memory)? > > > > > the reason we want to do it this way, btw, are to reduction of each of > > > the > > > single apps memory intake, on disk footprint and possibly of their > > > startup time. > > > > > your help will be appreciated. > > > > > tnx, GilkadH > > > > -- > > Dianne Hackborn > > Android framework engineer > > hack...@android.com > > > > Note: please don't send private questions to me, as I don't have time to > > provide private support, and so won't reply to such e-mails. All such > > questions should be posted on public forums, where I and others can see > and > > answer them. > > > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[android-developers] Re: creating a shared jar library
tnx Dianne. after my post i have learned about the ability to 'inject' my shared library into open source Andro, as described in: http://android.git.kernel.org/?p=platform/development.git;a=blob;f=samples/PlatformLibrary/README.txt;h=5ce9d2f7756a0708e9fc0aed7845f3d69d4a6ae0;hb=cupcake i take it this option still stands (again - only for open source platform), right? GiladH On Jul 30, 5:04 pm, Dianne Hackborn wrote: > Sorry, Android currently doesn't support third party shared libraries. > > > > On Thu, Jul 30, 2009 at 4:13 AM, GiladH wrote: > > > hey, > > > i have several apps (each in its own apk, process etc) running at the > > same time on user's device. > > > these apps are all linked to a single common jar file (internally > > devloped) which contains a large portion of their overall code size. > > > is there a way for me to force Andro to make this common jar load only > > once (e.g. into shared memory)? > > > the reason we want to do it this way, btw, are to reduction of each of > > the > > single apps memory intake, on disk footprint and possibly of their > > startup time. > > > your help will be appreciated. > > > tnx, GilkadH > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[android-developers] Re: creating a shared jar library
Sorry, Android currently doesn't support third party shared libraries. On Thu, Jul 30, 2009 at 4:13 AM, GiladH wrote: > > hey, > > i have several apps (each in its own apk, process etc) running at the > same time on user's device. > > these apps are all linked to a single common jar file (internally > devloped) which contains a large portion of their overall code size. > > is there a way for me to force Andro to make this common jar load only > once (e.g. into shared memory)? > > the reason we want to do it this way, btw, are to reduction of each of > the > single apps memory intake, on disk footprint and possibly of their > startup time. > > > your help will be appreciated. > > tnx, GilkadH > > > > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
