09-02-2018, 07:47 PM
Basically the interesting info in the PM is that the Xbox development kit only allows for creating and linking static libraries, not the standard shared ones. As per license terms, if you use a static version of a LGPL library in your project, you also must provide the means to anybody to relink your project with a different version of the library. In practice this means releasing the sources of your project, that is incompatible with any proprietary, commercial software.
I wouldn't ever enforce anybody to release their sources if using static Tilengine, that is silly, but the LGPL license requires this point to be satisfied. There is no conflict when using it as a shared library as I originally intended, but providing a console devkit that enforces using static libraries is just as silly as the LGPL requesting the freedom for the end user to relink it. The combination of both issues blocked grey to use Tilengine in a future console game. Sad!
The hurry to get a quick response was due to a deadline imposed by the game publisher to get a list of the tools that were going to be used in the development.
I wouldn't ever enforce anybody to release their sources if using static Tilengine, that is silly, but the LGPL license requires this point to be satisfied. There is no conflict when using it as a shared library as I originally intended, but providing a console devkit that enforces using static libraries is just as silly as the LGPL requesting the freedom for the end user to relink it. The combination of both issues blocked grey to use Tilengine in a future console game. Sad!
The hurry to get a quick response was due to a deadline imposed by the game publisher to get a list of the tools that were going to be used in the development.