> In both  CANAL and VSCP and in the upcoming uP code the lower
> levels are
> released under the LGPL. So there is no need to for a user app. using
> this stuff to release its code. The higher level  parts are GPL  just
> for sharing so if you use code from the upper levels you have
> to release
> your own code as well.
>
> If you compile something together and ship it to a customer and it
> contains GPL code I can't see why you should bother your
> customer with
> this fact. For the developer community however there should
> be a chance
> to get the source code from you in some open way.  It's that easy....

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

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products

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