> On Nov 13, 2016, at 1:30 PM, Daniel Roßberg <danielmrossb...@gmail.com> wrote: > > How do we handle LGPL version 2.1 incompatible licenses as the LGPL > version 3 used in FreeWRL? It should be possible to include it with > dynamical linkage, the usual way in BRL-CAD.
Yeah, LGPL dependencies are generally suboptimal for this very reason. For GCV, though, this was anticipated in the design (e.g., may even want to leverage commercial libs). We just have to integrate carefully and not allow any code/functions/ideas to migrate from the LGPL code to ours. Konrado set up cmake logic for FreeWRL, so that will need to be checked — to make sure it’s only compiling a dynamic lib. Ideally, FreeWRL should also live in a subdir of GCV, not over in src/other as a general dependency. Cheers! Sean ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
