3 ms·
But doesn't Google tries to avoid GPL? I think they're pretty anti-GPL with Android, and have some rules against inclusion of GPLed components there, besides t
by drdaeman 11y ago
But doesn't Google tries to avoid GPL?
I think they're pretty anti-GPL with Android, and have some rules against inclusion of GPLed components there, besides the kernel. I think the whole userspace is under non-copyleftish BSD/MIT/etc.
- asuffield 11y ago(Tedious disclaimer: not speaking for anybody else, my opinion only, etc. I'm an SRE at Google.) > But doesn't Google tries to avoid GPL? No. > I think they're pretty anti-GPL with Android, and have some rules against inclusion of GPLed components there, besides the kernel. OEMs don't want their hardware support to be GPL-encumbered. See https://source.android.com/source/licenses.html https://source.android.com/source/licenses.html
- saurik 11y agoThat's picking some major nits: whatever you want to claim is Google's internal mental opinion of GPL, the reality is they are building Android to cater to hardware manufactures, and those hardware manufactures do not want GPL, so Google has actively avoided GPL code in Android, often going to extreme lengths to build half-asses reimplementations of things that have perfectly stable GPL implementations so they don't have to rely on code using that license.
- Zigurd 11y agoThe JDK stays inside the development environment. The development toolchain translates Java bytecode to Dalvik bytecode. There are probably a few other GPL components in the toolchain, although they are transitioning away from GCC in the NDK.