MichaelMeissner:
One problem with using the LGPL, is it assumes a more traditional environment where programs are compiled into object modules that are linked against system libraries. However, in the Arduino IDE environment, it doesn't use object modules, except for the base avr libraries, and the modules provided by the compiler. All of the additional Arduino stuff above the base libraries is recompiled each time from scratch. Now, you could arrange to use make and more traditional object modules to comply with the LGPL. However, given this, it might be simpler to just switch to a more traditional environment, and don't use the Arduino IDE as well.Obviously, you have to go through each library that you use, to see what its copyright are, and either use it, or rewrite your own.
Sounds like you are also thinking it is not possible to comply with LGPL when using the Arduino IDE
to build the images.
Which kind of begs the question, of why the Arduino team went down the LGPL path for so much of their code
vs the GPL path given it looks like it isn't possible to comply with LGPL for closed source projects/products.
Quite likely it was a misunderstanding of the LGPL 2.x licensing terms for embedded projects/products.
--- bill