On Thu, Mar 6, 2008 at 10:50 AM, Gilad Ben-Yossef <[EMAIL PROTECTED]> wrote:
> Shachar Shemesh wrote: > > Amos Shapira wrote: > > > >> Another one is CodeSynthesis XSD > >> (http://www.codesynthesis.com/products/xsd/), it's GPL so we we can't > >> link it with our proprietary code. > >> > >> > > gcc is also GPL, and yet you can link the programs you compile with it > > to your proprietary code. > > hmpf... that's not a good example. > > It is true that GCC output (the object and ELF files) are themselves not > derived work of GCC. However, to actually use them for something you > need to link (statically or otherwise) with libgcc. > > Mind you, the produced programs are indeed not subect to the GPL - but > only because the FSF has made an explicit exception for libgcc. Whatever it is with GCC, libgxcc, mingw or whatever, the issue is that the codesynthesis program creates code which relies on linking with their own run-time libraries, which are covered by the GPL and therefore I can't link proprietary code with them and distribute them outside my own legal inetity, from http://www.codesynthesis.com/products/xsd/license.xhtml: By linking with the XSD runtime library and/or the generated code (directly or indirectly, statically or dynamically, at compile time or runtime), your application is subject to the terms of the GPL or the FLOSS Exception, which both require that you release the source code of your application if and when you distribute it. Distributing an application includes giving it to customers, contractors, parent companies, subsidiaries, or any legal entity other than your own. --Amos
