[Mono-list] runtime libraries vs class libraries

[Dave Curylo]

Normally, you're just linking to class libraries, not the runtime itself,
so you are linking to libraries distributed under the MIT X11 license.
 Mono.Security.dll, for example, is a class library.

If you look at the source of those Mono.Security classes, you will see a
nice, permissive license that tells you that you just have to retain the
copyright notice in the software, and it further limits their liability if
it doesn't work correctly.  Commercially friendly.

https://github.com/mono/mono/blob/master/mcs/class/Mono.Security/Mono.Security.X509/X509Stores.cs

You will see the same sort of license under anything in the mcs/class part
of the repo (the class libraries):
https://github.com/mono/mono/tree/master/mcs/class

You are only bound to the LGPL if you do things like static linking with
the runtime, as in with mkbundle --static or embedding mono.

Of course, it would be good to have a lawyer confirm your license
compliance.

On Friday, December 6, 2013, Edward Ned Harvey (mono) wrote:

>  I'm working on a commercial app that wants to use Mono.Security.  In
> Windows, this is located at
>
> C:\Program Files (x86)\Mono-3.2.3\lib\mono\4.0\Mono.Security.dll
>
>
>
> The mono eula says "The runtime libraries are under the GNU Library GPL
> 2.0 (LGPL 2.0).  The class libraries are released under the terms of the
> MIT X11 license."
>
>
>
> So which is it?  What are the runtime libraries, and what are the class
> libraries?  How do I know which is which?
>
>
>
> Thanks...
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-list/attachments/20131206/49cfb65d/attachment.html>