(05-30-2015, 10:04 PM)delroth Wrote: tueidj: system provided libraries are an exception to the GPL. In general it's widely accepted that stuff like msvcrt or d3d are system provided, and there is a wide range of precedent for that. Random Android libraries that we want to use in Dolphin are not in the same situation (note, however, that the same situation would apply to us using the standard Android SDK/NDK, from my understanding of the situation).
In the future this license change will also allow us to integrate with OSVR, which is licensed under Apache 2.0.
You're not supposed to link with anything that isn't part of the NDK since they are private APIs subject to change in the future. If that is what's happening with Dolphin then that is what should have been remedied, rather than changing the licence.
It seems like even though there was this big undertaking to change the licence, and now a long blog post article about it, nobody knows of any dependency that was causing a licence conflict?
(05-30-2015, 10:31 PM)Armada Wrote: From what I understand the GPL exempts you from having to provide the source code for those libraries, but you are still not allowed to link to those libraries if the licenses on them would affect your rights given under the GPL.That makes no sense in this case since the apache license doesn't require derivative works (i.e. the programs linking to the apache licensed libraries) to also use the same license. If it did, every program for android would be required to use it...
In other words, the System Library Exception exempts those libraries from the "infection" of GPL, but it does not allow those system libraries to infect the GPL.