Re: [Lazarus] GPL'ed projects and closed-sourced tools

2009-03-04 Thread svaa
In Ada language forum they have had many times this discussion. The following are the constant conclusions: Dynamic linking has nothing to do with GPL. If DLLs are GPL and you use them, you must grant access to the source of DLL, not to the full project. Static linking of GPL tools require you

Re: [Lazarus] GPL'ed projects and closed-sourced tools

2009-03-04 Thread Hans-Peter Diettrich
svaa schrieb: In Ada language forum they have had many times this discussion. The following are the constant conclusions: Dynamic linking has nothing to do with GPL. If DLLs are GPL and you use them, you must grant access to the source of DLL, not to the full project. Static linking of

Re: [Lazarus] GPL'ed projects and closed-sourced tools

2009-03-04 Thread Graeme Geldenhuys
On Tue, Mar 3, 2009 at 12:52 PM, Hans-Peter Diettrich drdiettri...@aol.com wrote: AFAIR there exists a requirement (how strong?), that a user shall be able to build the project from the source code, so that everybody can trust his selfmade binaries, and is not bound to binaries supplied by

Re: [Lazarus] GPL'ed projects and closed-sourced tools

2009-03-04 Thread Matt Henley
My understanding and I am not a lawyer is that you are correct.. The gpl faq addresses this ( http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html ): I'm writing a Windows application with Microsoft Visual C++ (or Visual Basic) and I will be releasing it under the GPL. Is dynamically linking

[Lazarus] GPL'ed projects and closed-sourced tools

2009-03-03 Thread Graeme Geldenhuys
Hi, I got told in the CodeGear newsgroups that if you create a GPL'ed project, the tools used to create that project must also be GPL'ed otherwise somebody might require a commercial compiler to compile the GPL'ed project. I have never heard anything like this before. As far as I understand, if

Re: [Lazarus] GPL'ed projects and closed-sourced tools

2009-03-03 Thread Michael Van Canneyt
On Tue, 3 Mar 2009, Graeme Geldenhuys wrote: Hi, I got told in the CodeGear newsgroups that if you create a GPL'ed project, the tools used to create that project must also be GPL'ed otherwise somebody might require a commercial compiler to compile the GPL'ed project. I have never

Re: [Lazarus] GPL'ed projects and closed-sourced tools

2009-03-03 Thread Graeme Geldenhuys
On Tue, Mar 3, 2009 at 11:56 AM, Funky Beast funkybe...@pacific.net.sg wrote: Well...lets see uhmm, there are mega-tons of GPL'ed Delphi projects on SourceForge, and Delphi is not a GPL'ed tool. There are also tons of GPL'ed VS projects on SourceForge, and VS is most definitely not a

Re: [Lazarus] GPL'ed projects and closed-sourced tools

2009-03-03 Thread Hans-Peter Diettrich
Graeme Geldenhuys schrieb: I got told in the CodeGear newsgroups that if you create a GPL'ed project, the tools used to create that project must also be GPL'ed otherwise somebody might require a commercial compiler to compile the GPL'ed project. AFAIR there exists a requirement (how

Re: [Lazarus] GPL'ed projects and closed-sourced tools

2009-03-03 Thread Marco van de Voort
On Tue, Mar 03, 2009 at 11:52:49AM +0100, Hans-Peter Diettrich wrote: otherwise somebody might require a commercial compiler to compile the GPL'ed project. AFAIR there exists a requirement (how strong?), that a user shall be able to build the project from the source code, so that

Re: [Lazarus] GPL'ed projects and closed-sourced tools

2009-03-03 Thread Hans-Peter Diettrich
Marco van de Voort schrieb: AFAIR there exists a requirement (how strong?), that a user shall be able to build the project from the source code, so that everybody can trust his selfmade binaries, and is not bound to binaries supplied by third parties. For this reason all modified source