This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Shared library that needs stuff from another library...
On Sep 8, 1999, Mark Crosland <mjc@c1000907-b.sttls1.wa.home.com> wrote:
> Providing libstdc++ with the product may not be that bad? Unless, of
> course there are any legalities involved?
There are. libstdc++ is GPLd, which means that, if you distribute it
in binary form, you must ensure that whomever gets it has access to
its sources. There's an exception to the GPL in libstdc++ that waives
this restriction from derived works compiled with a GNU compiler,
otherwise your own code would have to be GPLed too. But the fact that
you can distribute your code without sources doesn't allow you to do
the same with libstdc++. So you must either ship it in source and
binary form along with your program or you must make the sources
available upon request, as specified in the GNU GPL.
> Whether the code is statically or dynamically linked, it's it still
> being used in the same way...
The FSF states there's no difference between static or dynamic
linking, in terms of determining whether your work is a derived work
of the library or not.
--
Alexandre Oliva http://www.dcc.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{dcc.unicamp.br,guarana.{org,com}} aoliva@{acm.org,computer.org}
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
** I may forward mail about projects to mailing lists; please use them