On 31 May 2002 08:10:17 +0930
David Fitch <[EMAIL PROTECTED]> wrote:

> so if I develop some application on linux and compile with gcc 

Programs compiled with gcc which do not include any GPL or LGPL code
are specifically exempt. 

> and use
> standard header files/libs (eg. glib) then that will be linked into
> my binary I produce.  

It depends on the library. If the library is GPL you must release the
source. If it is LGPL you can dynamically link and avoid releasing the
source.

Glibc (the main C library on Linux) is LGPL. Therefore Real Networks
can release RealPlayer which links against glibc without releasing the
source.

I believe (but don't take my word for it) that GTK+ and GLIB are 
also LGPL. The X libraries are under another license again but one that
does allow their use in commercial apps.

> If I want to sell commercially my app, do I
> have to give away the source too?  

See above.

> all the source or just the GPL bits?

If you link against GPL code then you must release the source. All of it.

> if I don't include the source do I have to acknowledge the GPL stuff
> or include the GPL copyright notice etc etc?

You don't need to include the source. You do need to make it available. 
If you don't make it available, you are in breach of the GPL.

Erik
-- 
+-----------------------------------------------------------+
  Erik de Castro Lopo  [EMAIL PROTECTED] (Yes it's valid)
+-----------------------------------------------------------+
"Having a firewall that allows NFS to the Internet is like having a 
seat belt that lets your head touch the dashboard." -- Marcus Ranum
-- 
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug

Reply via email to