Loading dynamic linked libs from memory, violation of LGPL?

[Stefan Lundmark]

Hi,

I know the best answer I can get is to ask a lawyer, but I'm only curious.

We have a non-officially distributed prototype with some linked dynamic libraries to it, but package it all up into a big archive.
Since the DLL's are no longer visible to the outside (ie, they're not in the game folder) - would this be a violation? They're still dynamically linked however they're loaded from memory.

I know the guys at FMOD (it's not LGPL, nut dynamically linked) have reasons for dynamic linking and that's to see who's using the library.
Thoughts?

[jacmoe]

No thoughts.

Dynamic linking is dynamic linking.
Putting it all in a big zip doesn't change that. IMO.

[haffax]

The basic idea of the LGPL is this: The user should theoretically be able to compile its own version of the LGPL licensed library to replace the one you deliver. Whether this is sensible or technically feasible is another question. But you are on the safe side, when the user can unpack the archive replace the DLL with its own and repack the archive.

[reptor]

Thankfully from 1.7 onwards we don't have to think about that kind of things as the license is a different one.

[Stefan Lundmark]

Thankfully from 1.7 onwards we don't have to think about that kind of things as the license is a different one.

Uh, there are other libraries than OGRE out there. Hence why this is placed under "Off-topic" - it had nothing to do with OGRE. But yeah, 1.7 looks awesome indeed.

[reptor]

Oh, sorry

I use the "view new posts" and I admit I don't pay much attention to the name of the board when reading and replying to what other people have posted.