The main sentence I'm pointing is:
*You are not responsible for enforcing compliance by third parties with
this License. *
Also about PS4:
- *WebKit *- http://doc.dl.playstation.net/doc/ps4-oss/webkit.html
- *Cairo *- http://doc.dl.playstation.net/doc/ps4-oss/cairo.htm
- *Mono VM* - ht
On 07/12/2016 04:28 PM, Aleksandr Palamar wrote:
> Yes, of course those platforms have DRM. But GLib, GObject and GIO are
> available under LGPL 2.1, which states:
>
> *10.* Each time you redistribute the Library (or any work based on the
> Library), the recipient automatically receives a license
Yes, of course those platforms have DRM. But GLib, GObject and GIO are
available under LGPL 2.1, which states:
*10.* Each time you redistribute the Library (or any work based on the
Library), the recipient automatically receives a license from the original
licensor to copy, distribute, link with o
Does XBox One / PS4 have DRM that prevents relinking? Even a translation
layer may not work. I’m doubtful GLib is compatible with PS4. Please
note that it is *not* compatible with Apple app stores. Asking the FSF
may indeed be a good idea.
___
vala-list m
I suspect that Jens talks about creating a "translation layer" that
offers to the unmodified GLib all the system calls that it expects, like
"fopen, printf" and so on.
El 11/07/16 a las 17:42, Aleksandr Palamar escribió:
> Jens, do you mean something like linking GLib to your ownn closed source
>
Mmmm... that's a tricky question: you only need to grant access to the
modified sources to the people to whom you distributed the binaries.
This is: if you create a game with a modified GLIB library, and you sell
that binary game only to me, you must grant access to the modified
sources only to me,
