| |||||||||||||
|
| |||||||||||||
Welte: Android Mythbusters (Matt Porter)Welte: Android Mythbusters (Matt Porter)Posted Nov 5, 2009 23:52 UTC (Thu) by jgg (guest, #55211)In reply to: Welte: Android Mythbusters (Matt Porter) by pboddie Parent article: Welte: Android Mythbusters (Matt Porter)
IMHO, android's libc is probably the best next option to glibc. The other choices leave alot to be desired, and are fairly disused these days.
Indulging internal developers is quite an interesting point.. Who ever created some of this stuff is really good. There are not many people in the world who could sit down and write a new ELF dynamic loader, libc and related toolchain goop - let alone start out that way and not be afraid of failing. This is arcane stuff.
I'd be quite interested to know how long it took to make, IMHO, a super expert, done this before, kind of thing, could probably knock it out in a month. You'd probably burn more time than that just fussing with glibc to make it smaller.
(Log in to post comments)
Welte: Android Mythbusters (Matt Porter) Posted Nov 6, 2009 13:35 UTC (Fri) by nix (subscriber, #2304) [Link]
uClibc is 'fairly disused'? Not in my embedded world :)
(oh, and most of this stuff is dull and fiddly but not *hard*. At least
Welte: Android Mythbusters (Matt Porter) Posted Nov 6, 2009 13:40 UTC (Fri) by pboddie (guest, #50784) [Link]
Can you comment on dietlibc, newlib and uClibc? I wasn't aware that these were particularly deficient, although I'm sure that there are good reasons for not choosing them in certain situations.
|
|
||||||||||||