Page 2 of 2

Re: Engine3D etc also as static libs

Posted: Thu Nov 10, 2011 4:33 pm
by J. Baker
ts-soft wrote:
J. Baker wrote:I don't see why not.
For example some DLLs have a license for freeware and a license for commercial programs. The Author will always
see if anyone use his DLL :wink:
Mostly is only forbidden to include it and use from memory like molebox oder memorymodule, but not including in
a installprogram. Some DLLs make a selftest on loading and don't work from memory or container.

Greetings - Thomas
I understand what you're saying now but I'm not talking about running it from memory. Just including it in the executable itself and "installing" it to a folder at first runtime. There after, calling it from the folder it was installed to. Pretty much like a installer. ;)

Re: Engine3D etc also as static libs

Posted: Thu Nov 10, 2011 5:41 pm
by Foz
Fred wrote:The main engine could be, but we have included some dependencies which would have to stay in DLL due to the LGPL license.
That's interesting - what components are they?

Just so I can keep an eye on them in case they change license :)