Lesser GPL and "dynamic linking"

[Paul E Collins]

I'm considering using the NetSpell spell checking engine in my
application.

However, NetSpell is licensed under the Lesser GPL, and I want to
withhold my application's source code. The licence states that I can
do this if I link to the NetSpell library dynamically (rather than
compiling against it statically). How can I achieve this in C#?

P.

[Tom Shelton]

In article <ci**********@hercules.btinternet.com>, Paul E Collins wrote:

I'm considering using the NetSpell spell checking engine in my
application.

However, NetSpell is licensed under the Lesser GPL, and I want to
withhold my application's source code. The licence states that I can
do this if I link to the NetSpell library dynamically (rather than
compiling against it statically). How can I achieve this in C#?

P.

You can't staticly link to it from C# anyway - so I think your ok :)

--
Tom Shelton [MVP]

[Frans Bouma [C# MVP]]

Paul E Collins wrote:

I'm considering using the NetSpell spell checking engine in my
application.

However, NetSpell is licensed under the Lesser GPL, and I want to
withhold my application's source code. The licence states that I can
do this if I link to the NetSpell library dynamically (rather than
compiling against it statically). How can I achieve this in C#?

The LGPL is meant to solve the 'dynamic/static linking' issue of the GPL. In
other words: you can safely link to it in any form, without having to open up
your own sourcecode. The LGPL only states that if you add / alter code of the
LGPL-ed library, and you distribute that new code in binary form, you have to
supply the library's sourcecode as well.

Frans.

--
Get LLBLGen Pro, productive O/R mapping for .NET: http://www.llblgen.com
My .NET Blog: http://weblogs.asp.net/fbouma
Microsoft C# MVP