06.07.2013, 10:00, "Matthew Mondor" <mm_li...@pulsar-zone.net>: > On Sat, 06 Jul 2013 09:38:20 +0400 > Anton Vodonosov <avodono...@yandex.ru> wrote: > >>> 1 - Licensing/the ecl-android build process. ECL is LGPL, which means I >>> can't statically link against it without open sourcing my project (which I >>> can't), but ecl-android generates a static library for it. Since there are >>> so many files and generators, I don't even know where to start to change it >>> to a shared library. >> You are mistaken here - you can link with LGPL libraries without open >> sourcing your code. >> This is exactly the difference between GPL and LGPL. > > Unless I'm mistaken (disclaimer: I'm no lawyer), dynamic linking is > fine, as it allows to fulfill the requirement that the user be able to > upgrade the LGPL dependencies, while static linking might be > problematic... > -- > Matt
Ah, yes, it is me who is mistaken. Indeed, static linking requires your code to be open sourced. ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
