[Bf-cycles] C++ API and the GPL

Tom M letterrip at gmail.com
Wed Nov 16 20:20:09 CET 2011

Actually one way to do it is to construct a BSD licensed standalone
implementation of the API and then compile Octane against the
standalone API.  As long as the standalone and Blender internal API
are binary compatible it should work without there aren't likely any
legal issues.

Also it isn't even clear that the interpretation of the GPL that says
no linking of proprietary software has any force here.  The GPL
restricts those who redistribute Blender, and likely can't be used to
enforce restrictions on 3rd parties usage of an API.


On Mon, Nov 14, 2011 at 11:51 PM, Dan Eicher <dan at trollwerks.org> wrote:
> On Mon, Nov 14, 2011 at 11:10 PM, Ben Dansie <bendansie at hotmail.com> wrote:
>> Hi All,
>> I think it was meant in terms of Vray can't link to Blender via the api, not
>> 3dsmax can't link to Cycles. If this is actually the case regarding the api
>> then it's more of an issue imho.
>> Could be wrong.
>> Cheers,
>> Ben
> Ya, the octane guys are looking for someone to do a full integration
> but it looks like it's unpossible other than going the (slow) python
> route.
> Dan
> _______________________________________________
> Bf-cycles mailing list
> Bf-cycles at blender.org
> http://lists.blender.org/mailman/listinfo/bf-cycles

More information about the Bf-cycles mailing list