No subject

"For example, if you distribute copies of the library, whether gratis or
for a fee, you must give the recipients all the rights that we gave you.
You must make sure that they, too, receive or can get the source code.
If you link other code with the library, you must provide complete
object files to the recipients, so that they can relink them with the
library after making changes to the library and recompiling it. And you
must show them these terms so they know their rights."

"6. ....
a) Accompany the work with the complete corresponding machine-readable
source code for the Library including whatever changes were used in the
work (which must be distributed under Sections 1 and 2 above); and, if
the work is an executable linked with the Library, with the complete
machine-readable "work that uses the Library", as object code and/or
source code, so that the user can modify the Library and then relink to
produce a modified executable containing the modified Library. (It is
understood that the user who changes the contents of definitions files
in the Library will not necessarily be able to recompile the application
to use the modified definitions.)"

Which basically says that you can either dynamically link the library or
you can staticly link the library if you provide .o files for you
application so that the end user can relink with a new version of the
library. It also says you can leave the .o files and source for the
library on the web somewhere rather than including it with the
distribution.

Please, read the license. These are important documents. It makes me
very sad to meet programmers who have never read the GPL and LGPL. Its a
lot like the feeling I get when I meet Americans who have never read the
Declaration of Independence and the Constitution. 

	Bob Pendleton

-- 
+------------------------------------+
+ Bob Pendleton is seeking contract  +
+ and consulting work. Find out more +
+ at http://www.jump.net/~bobp       +
+------------------------------------+