Re: OpenMW Andriod -- Graphics Issues... Any Ideas?
Posted: 13 Nov 2018, 09:22
I'm do not want to play hard ball here, I've personally helped sandstranger when Bethesda contacted him.[1] I've helped, where I could, any and all people who have wanted to port OpenMW to Android. Yes, I have an invested invested interest here and I see it as a betrayal of trust and time wasted when all I wanted was to see that OpenMW could be built for Android in a reproducible way for everyone and not tucked away in another website behind a registration.
Can anyone give a reason why one would want to hide the source code?
I mean, the official android port is here:
https://github.com/OpenMW/android-port
It hasn't been updated/touched since Feb 15. So what has happened is that a fork has happened with this code and binaries released with the code from this other fork. All we ask is that the work be contributed back. Is this a problem?
That being said, sandstranger's argument is only half-true, the final result is a binary that incorporates GPLv3 code. That means everything the GPLv3 code touches also becomes GPLv3, when you release the APK file. That is the essence of a derived project.[2][3]
So even if the 'java code' is under another license, the moment you create an APK with OpenMW, the GPLv3 applies to the _whole_ package, including the 'java code' that is bundled with OpenMW. That is how the GPLv3 works.
To escape the requirements of the GPLv3 you would have to re-write OpenMW from scratch using another license. Had OpenMW been licensed under the LGPLv3 then you could link to OpenMW and preserve the 'java code' under your license.
[1] https://wiki.openmw.org/index.php?title=Bethesda_Emails
[2] http://rusgpl.ru/
[3] http://antirao.ru/gpltrans/gplru.pdf
Can anyone give a reason why one would want to hide the source code?
I mean, the official android port is here:
https://github.com/OpenMW/android-port
It hasn't been updated/touched since Feb 15. So what has happened is that a fork has happened with this code and binaries released with the code from this other fork. All we ask is that the work be contributed back. Is this a problem?
That being said, sandstranger's argument is only half-true, the final result is a binary that incorporates GPLv3 code. That means everything the GPLv3 code touches also becomes GPLv3, when you release the APK file. That is the essence of a derived project.[2][3]
So even if the 'java code' is under another license, the moment you create an APK with OpenMW, the GPLv3 applies to the _whole_ package, including the 'java code' that is bundled with OpenMW. That is how the GPLv3 works.
To escape the requirements of the GPLv3 you would have to re-write OpenMW from scratch using another license. Had OpenMW been licensed under the LGPLv3 then you could link to OpenMW and preserve the 'java code' under your license.
[1] https://wiki.openmw.org/index.php?title=Bethesda_Emails
[2] http://rusgpl.ru/
[3] http://antirao.ru/gpltrans/gplru.pdf