On Mon, Jun 01, 2015 at 08:25:59PM -0400, Neil Cherry wrote:
> I'm pretty sure the LGPL is for the libraries so sharing your main
> sketch code or your own private libraries are not required.

Yes, you're right, if you're talking about source code.

As soon as you distribute firmware which has an LGPL licensed library
inside it, you trigger the distribution terms of the LGPL license.

Then the object files are required ... if the linker being used
requires them.

If you substitute your own linker method, such as by partial flash
programming, and a discoverable jump table, you can avoid the object
files.

> I have read the licenses (oi!) and hope I understand them. ;-)

;-) Me too.  Years of practice at using them.  Had a job once that
required me to advise people about them, to protect corporate
interests.

> The V3 of the GPL and LGPL can toss a wrench in the works so try to
> avoid code using those licenses.

Agreed.  But
http://www.gnu.org/licenses/gpl-faq.en.html#LGPLStaticVsDynamic is
about both v2, v2.1, and v3 of the LGPL.

--=20
James Cameron
http://quozl.linux.org.au/
--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.