tinycc-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tinycc-devel] Tinycc-devel Digest, Vol 129, Issue 4


From: Graham Swallow
Subject: Re: [Tinycc-devel] Tinycc-devel Digest, Vol 129, Issue 4
Date: Fri, 3 Jan 2014 20:22:29 +0000

You can link an LGPL library into a proprietary binary, PROVIDED,
the end user can relink the same LGPL library into a similar binary.

You need to provide your binary as a link-kit, to allow this.
With symbols, and a makefile. A pre-built .exe is what the installer uses.
They can then relink with an adjusted LGPL library.

This has always raised question of inline functions and macros,
especially with C++, but that is the nature of the language.

Its still advantageous to the OSS community,
because the LGPL components get support, USED, etc,

Graham


On 3 January 2014 17:00,  <address@hidden> wrote:
> Send Tinycc-devel mailing list submissions to
>         address@hidden
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.nongnu.org/mailman/listinfo/tinycc-devel
> or, via email, send a message with subject or body 'help' to
>         address@hidden
>
> You can reach the person managing the list at
>         address@hidden
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Tinycc-devel digest..."
>
>
> Today's Topics:
>
>    1. Re: linking tinycc (Christian Jullien)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 3 Jan 2014 08:23:10 +0100
> From: "Christian Jullien" <address@hidden>
> To: <address@hidden>
> Subject: Re: [Tinycc-devel] linking tinycc
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset="us-ascii"
>
> Good question,
>
>
>
> Here is my understanding:
>
> Because of COPYING which states that tcc is LGPL, I would say NO unless your
> project is GPL but there is an attempt to move tcc to a BSD like license
> (see RELICENSING).
>
> At that time, we've got no reply from some maintainers.
>
>
>
> As I understand from RELICENSING, tcc for x86_64 elf (only) is safe to
> static link (if you add copyright notice) while tcc for arm is still using
> LGPL by default which prevents you to statically link with tcc unless your
> whole project is also GPL.
>
>
>
> It would be nice to clarify if maintainers not having replied say Yes or say
> No.
>
>
>
> Christian
>
>
>
> From: address@hidden
> [mailto:address@hidden On Behalf Of
> Julien Zefi
> Sent: vendredi 3 janvier 2014 06:53
> To: address@hidden
> Subject: [Tinycc-devel] linking tinycc
>
>
>
> can i link the static version of tinycc in my program without face any
> licensing problem ?
>
>
>
> J. Z.
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <http://lists.nongnu.org/archive/html/tinycc-devel/attachments/20140103/21a55b12/attachment.html>
>
> ------------------------------
>
> _______________________________________________
> Tinycc-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/tinycc-devel
>
>
> End of Tinycc-devel Digest, Vol 129, Issue 4
> ********************************************



reply via email to

[Prev in Thread] Current Thread [Next in Thread]