According to GNU's site, if you statically link with GLib, you have to at least provide users with object files (not necessarily sources) so that they can link against any version they like of the library under the LGPL. https://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynamic For the rest, I cannot tell, but I'm pretty sure that LGPL is sufficiently permissive. Le lundi 11 juillet 2016 à 16:29 +0300, Aleksandr Palamar a écrit :
Hi, Vala-List users. I'm curious about GLib license (which is the core of Vala runtime), mainly because I'm thinking about using Vala in closed source (or zlib if that would be possible in future) project, which may (or not) be used on different platforms including iOS (which doesn't allow dynamic linkage), PS4 and XBoxOne. Would it require to make application available under LGPL as well or I would able to kept application under any license I like while sharing (if target platform allows it, because I doubt about PS4 and XONE) changes for GLib if there was any. Just don't want to go wrong way and force myself to drain inside license problems in future. Regards, Aleksandr Palamar _______________________________________________ vala-list mailing list vala-list gnome org https://mail.gnome.org/mailman/listinfo/vala-list
-- Guillaume Poirier-Morency <guillaumepoiriermorency gmail com> Étudiant au baccalauréat en Informatique à l'Université de Montréal Développeur d'application web Mon blog: https://arteymix.github.io/ Mon projet de coopérative: https://pittoresque.github.io/ Clé PGP: B1AD6EA5
Attachment:
signature.asc
Description: This is a digitally signed message part