[Bf-committers] libreDWG

François T. francoistarlier at gmail.com
Wed Aug 25 15:00:16 CEST 2010


hum, seems like some Py binding has been started on this :
http://libreplanet.org/wiki/LibreDWG#Bindings_and_extensions
http://git.savannah.gnu.org/cgit/libredwg.git/tree/bindings/python



2010/8/17 François T. <francoistarlier at gmail.com>

> bloody hell, it is complicated !
> So maybe it would be better to compile the lib, then bind it w/ python and
> make it an addon for easier distribution ?
>
>
> François,
>
>
> 2010/8/16 Ralph Giles <giles at thaumas.net>
>
> On 16 August 2010 10:14, Martin Poirier <theeth at yahoo.com> wrote:
>>
>> > For audaspace it doesn't matter (LGPLv3 doesn't force anything on the
>> rest of the code).
>>
>> LGPLv3 doesn't force anything on the rest of the code, but the GPLv2
>> does force things on the LGPLv3. That is, the additional protections
>> of software freedom incorporated from the GPLv3 in the LGPLv3 count as
>> "additional restrictions" as far as the GPLv2 is concerned. I believe
>> linking is thus forbidden under the GPLv2's strong-copyleft
>> provisions, unless the library falls under the "system library"
>> exception. Which wouldn't be the case for a dependency included in the
>> blender tree. Therefore any GPLv2+ code gets upgraded to the GPLv3,
>> and any GPLv2-only code is a problem.
>>
>> This was discussed recently in the context of the gnome project. See
>> for example starting here:
>> http://mail.gnome.org/archives/desktop-devel-list/2010-July/msg00097.html
>>
>>  -r
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-committers
>>
>
>
>
> --
> ____________________
> François Tarlier
> www.francois-tarlier.com
> www.linkedin.com/in/francoistarlier
>



-- 
____________________
François Tarlier
www.francois-tarlier.com
www.linkedin.com/in/francoistarlier


More information about the Bf-committers mailing list