| |||||||||||||
Has Bionic stepped over the GPL line?Has Bionic stepped over the GPL line?Posted Mar 21, 2011 16:23 UTC (Mon) by swetland (subscriber, #63414)In reply to: Has Bionic stepped over the GPL line? by viro Parent article: Has Bionic stepped over the GPL line?
Bionic development started in late 2005 / early 2006, iirc. We explored a number of alternatives before settling on "BSD-libc-based with homegrown syscall and thread glue" which has worked pretty well.
The scripted processing of headers is a result of hand-curation of headers not scaling well. The goal is (obviously, I thought!) to extract the necessary userspace interface to the kernel without picking up internal-only or incompatible-with-userspace headers or subsections. At the time we got started it appeared that other libc projects were mostly doing this by hand.
We'll want to take a look at exclusion methods used by "make headers_install" -- if they provide a way to further reduce the scope of exported headers that's definitely interesting.
We strongly discourage the use of #include <linux/...> in Android userspace code, unless it's code that's directly talking to a kernel interface defined in that space -- primarily to keep things clean and reasonably portable.
(Log in to post comments)
Has Bionic stepped over the GPL line? Posted Mar 21, 2011 17:01 UTC (Mon) by viro (subscriber, #7872) [Link]
See include/Kbuild, include/linux/Kbuild, etc. Or just git grep header-y.
That's what gives the list of headers being exported. As for the rest - trimming is done by scripts/headers_install.pl, all of a screenful of it...
|
|||||||||||||