Note that this does NOT replace Bionic with glibc. Instead, we just use
the /bin/ and /lib/ directories which aren't being used by Android to
host a glibc-based stack. The BusyBox included, for instance, is linked
against glibc.
As always, feedback welcomed.
--
Karim Yaghmour
CEO - Opersys inc. / www.opersys.com
http://twitter.com/karimyaghmour
Cheers,
Nathaniel
> --
> You received this message because you are subscribed to the Google Groups
> "android-platform" group.
> To post to this group, send email to android-...@googlegroups.com.
> To unsubscribe from this group, send email to
> android-platfo...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/android-platform?hl=en.
>
If you ever do that, I'd be more than happy to include it as an option
in Cyborgstack. Currently I'm hosting every "major" feature as a
separate branch, but I'm planning to merge it all into a single branch
as soon as I can find a satisfactory configuration system for it all.
Currently the most obvious option would be the kernel's Kconfig, but I
suspect it's tightly tied to the use of recursive build systems (which
the AOSP isn't using.) And the AOSP's "CAPITALIZED_FEATURE_FLAGS=foo"
method is ok if and only if you know ahead of time the entire feature
list, which isn't going to be the case with something like Cyborgstack.
--
Karim Yaghmour
CEO - Opersys inc. / www.opersys.com
http://twitter.com/karimyaghmour
--
Karim Yaghmour
CEO - Opersys inc. / www.opersys.com
http://twitter.com/karimyaghmour
Cheers,
Nathaniel
On Sun, Feb 19, 2012 at 7:39 PM, Karim Yaghmour