diff options
Diffstat (limited to 'pipermail/nel/2001-December/000812.html')
| -rw-r--r-- | pipermail/nel/2001-December/000812.html | 77 |
1 files changed, 77 insertions, 0 deletions
diff --git a/pipermail/nel/2001-December/000812.html b/pipermail/nel/2001-December/000812.html new file mode 100644 index 00000000..adb0a0a7 --- /dev/null +++ b/pipermail/nel/2001-December/000812.html @@ -0,0 +1,77 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Nel] Using GCC? -- was: GPL specifics</TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:archer%40frmug.org"> + <LINK REL="Previous" HREF="000811.html"> + <LINK REL="Next" HREF="000795.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Nel] Using GCC? -- was: GPL specifics</H1> + <B>Vincent Archer</B> + <A HREF="mailto:archer%40frmug.org" + TITLE="[Nel] Using GCC? -- was: GPL specifics">archer@frmug.org</A><BR> + <I>Fri, 14 Dec 2001 14:41:33 +0100</I> + <P><UL> + <LI> Previous message: <A HREF="000811.html">[Nel] Using GCC? -- was: GPL specifics</A></li> + <LI> Next message: <A HREF="000795.html">[Nel] Gamer question</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#812">[ date ]</a> + <a href="thread.html#812">[ thread ]</a> + <a href="subject.html#812">[ subject ]</a> + <a href="author.html#812">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>According to Tony Hoyt: +><i> Okay well I hate to go slightly off topic here but this is a question +</I>><i> that I need to ask since we're talking about all GPL, LGPL, etc. Where +</I>><i> does building an application with gcc fall into all of this? I write a +</I>><i> program, build it with gcc or g++ and plan to sell it to other users. +</I>><i> But, I don't want to distribute the source of the application. Can I +</I>><i> still use gcc/g++? or am I forced to find an alternative compiler such +</I>><i> as VisualC for windows or a unix specific compiler for unix variants? +</I> +Even though you *used* GCC to build the program, gcc *itself* is in no +way present in the program you distribute. There's no portion of gcc +source code or binary in your application. Thus, your program does not +inherit the licensing from the gcc GPL license. + +The only think that gets bundled is the C library. And the C library +(glibc) is covered by the LGPL, which specifically allows for that case +(i.e. distributing a program that is linked with a GPL software, without + placing the GPL strictures on the program itself). + +The same thing would apply to a C grammar parser that was generated +by bison (the GPL parser generation tool). Using bison to generate your +C source does not require you to put said source under the GPL: bison +is not included in your program, only its output (hmmm, is the library +required for bison LGPL? I think so, but can't remember) + +-- + Vincent Archer Email: <A HREF="mailto:archer@frmug.org">archer@frmug.org</A> + +All men are mortal. Socrates was mortal. Therefore, all men are Socrates. + (Woody Allen) + +</pre> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI> Previous message: <A HREF="000811.html">[Nel] Using GCC? -- was: GPL specifics</A></li> + <LI> Next message: <A HREF="000795.html">[Nel] Gamer question</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#812">[ date ]</a> + <a href="thread.html#812">[ thread ]</a> + <a href="subject.html#812">[ subject ]</a> + <a href="author.html#812">[ author ]</a> + </LI> + </UL> +</body></html> |