Re: [Tinycc-devel] License is too restrictive for real-world use.

[Nids]

The LGPL actually states that the modified *source code* must be made available and redistributed and this solves the problem of static vs dynamic linking at the very beginning.

If the modified library changes the interfaces with respect to the original one, there is no way you can make that work with dynamic libraries anyway.

Typed on a very small keyboard...

---

From: Sean Conner
Sent: ‎02/‎03/‎2016 08:35
To: address@hidden
Subject: Re: [Tinycc-devel] License is too restrictive for real-world use.

It was thus said that the Great Nids once stated:
> John B said:
> > Please, if you want to consider tinycc being more relevant than it is, and
> > being adopted in big ways so that people can build push calls instead of
> > pull scripts, it just hinges on dropping the toxic lgpl and switching to
> > e.g. bsd.  There are so many things I want to do with tinycc but that is
> > not why I want to be a developer.  Not until I win the lottery, anyway.
>
> Ehm... No.
> 
> The LGPL just states that when you redistribute your product, the code of
> TinyCC, or its modified version, must be redistributed/made available. The
> same does NOT apply to the code that links against it.

  The other term (or restriction, depending upon your view point) is that
the user needs to be able to use a modified version of the LGPL library in
the product.  Making TCC a shared library makes this easy to do (since the
user can then replace the with their own modified TCC).  Using a statically
compiled LGPL library is a bit tougher---you have to provide all the object
files to relink the product with their own version of TCC (in this case).

  -spc


_______________________________________________
Tinycc-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/tinycc-devel