Re: [Mingw-cross-env-list] Congrats - short question.

[Jos De Laender]

Op 31/01/2016 om 11:59 schreef Nagaev Boris:
> <snip>
> > Remark 2 : unless you are developing GPL open source you will want to use
> > the shared build in order to avoid (L)GPL violations.  Having said that,
> > licensing is complex business and a static build can violate licenses even
> > if you are releasing under the GPL. The same goes for shared builds, but
> > your odds are better.
> -1 for this. Static builds are convenient to distribute. AFAIK,
> static/shared linking doesn't matter for (L)GPL, if you provide
> sources or object files.
This is a minefield and my explanation wasn't overly clear in the first 
place either.

1. You are developing a GPL application : probably (*) you are fine when 
you distribute your sources and the sources of the used libraries (or 
refer to it). Whether you use static or shared.

2. You are developing a non-GPL application :

2.a. I doubt (*) if you can distribute as static without violating LGPL 
(which many of the MXE compiled libs are). Some people state it's fine 
if  you provide instructions how to re-link with new versions of the 
underlying LGPL libs, but I'm not sure that makes sense or is practical.

2.b. I think (*) you can distribute as shared and where the LGPL 
libraries are in a dll. For GPL libraries you still would have an issue 
though.

(*) In any case, again, this is complex and specialized and in doubt you 
should seek legal advice.



> > <end suggestion>
> >
> > Many thanks,
> >
> >
> >
> > --
> > Jos De Laender
> >
> > http://www.jodela.be
> > https://www.de-laender.be:9961
> >
> >
> > ---
> > Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware.
> > https://www.avast.com/antivirus

--
Jos De Laender

http://www.jodela.be
https://www.de-laender.be:9961


---
Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware.
https://www.avast.com/antivirus