To expand on David's remarks a bit, bionic exists for two reasons:

- To provide a small embedded libc

- To meet the license goals of the core android platform, which are:
  - GPL for the Linux kernel and drivers
  - Apache2/BSD/MIT whenever possible for userspace

One of my hopes is that over time we can reduce the footprint of the 
core platform (by a combination of putting various modules on a diet 
and also making the core build more configurable so unneeded components 
may be more easily omitted).

Brian

[David Turner <[EMAIL PROTECTED]>]
> There is absolutely zero chance that GLibc becomes part of the Android
> open-source platform for licensing reasons.
> (same for uCLibc, KLibc, DietLibc and EGlibc by the way)
> 
> That doesn't mean that we are totally opposed to people providing patches
> that would allow to use the Android
> sources with GLibc, but we are not going to support this effort (which means
> that if some of our changes break
> a GLibc system, that will be *your* problem, patches welcome).
> 
> Also, we make absolutely no guarantee about the correct behaviour of a
> GLibc-based Android system,
> *especially* with regards to security.

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [EMAIL PROTECTED]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to