David, i am not sure that. i know it's possible to link a lite libc in dynamic linker. but i read through the file Android.mk and didn't spot any difference of regular libc. do you have any direct evident?
thanks, --lx On Sun, Jul 18, 2010 at 2:02 PM, David Turner <di...@android.com> wrote: > The dynamic linker uses a special version of the static c library. The > shared c library is used by other shared libraries and dynamic > executables. > > Prelinking is only an optimization used to speed up shared library > loading and reducing their sizes. It is not required. > > Regards. > > On Friday, July 16, 2010, Liu Xin <navy.x...@gmail.com> wrote: > > Hi Developers, > > > > i can't work out this problem. how linker uses libc? dynamic liner in > android(bionic/linker) seems to link bionic(libc) without abnormal things. > > is the libc static or dynamic? if it is static, then why we bother build > it to a shared library? > > or if it is static, can normal program reuse the static libc later on? > > > > btw, is prelink(apriorio) optional? if i globally forbids it in build, > can android system still start up? > > > > Thanks, > > --lx > > > > > > > > -- > > unsubscribe: > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> > > website: http://groups.google.com/group/android-porting > > > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
