Well, in the case of the GPL this is the intent and I don't see a real
significant difference between embedded and any other proprietary
software. The LGPL however looses a little of it's intent, so use the
LGPL with static linking exceptions. See SSCILIB for an example of a
project with that license.

One can certainly debate weather most companies would want to use
L/GPLed code in their products but thats really not a new argument or
one thats embedded specific.

Personally, If I were making a commercial product (major speculation
zone considering I've never been anywhere near the creation of a
commercial product) I doubt I'd much care about using LGPL w/Static
exception. As for regular GPL/LGPLed code, thats harder to say, it
depends on how much of my product was based on nifty code.

-- Mike

>My comment was on uC code. If I use GPL or LGPL code in my commercial uC
>application I am forced to open *all* code of my application (unless the
>license is LGPL and my uC support dynamic linking, the latter is not
>very practical on a PIC).
>
>Wouter van Ooijen
>
>

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.