Lpc2000

Here's my 2 cents on this. I think the LGPL was intended to cover all
kinds of "libraries" in a very generic sense. I think it was intended
to allow people to link their proprietary project against a "chunk of
code" covered under LGPL, and still be OK with commerical deployment
without requiring the rest of the source to be open.
  I think of "shared" in the sense of being "reusable" or "linkable"
as separate units. I don't think they meant that many programs on one
computer had to be able to use it. I think they were talking about
cross computer shared modules in a very generic way.
  A lot of people link to LGPL libraries with gcc and the deploy to
microcontrollers without releasing the entire source of their project.
The gcc compiler would be almost useless if you couldn't link to their
libraries and still keep your main source code protected.
  A lot of people don't know this, but even GPL (I'm not talking about
LGPL here) code can be used inside a company without requiring the
entire source code base to be released publicly. The GPL license is
all about public distribution. If your final product is only used
within a company and is never publicly released, then you don't need
to publicly release your source code, even for GPL code. But, the
minute you start selling controllers to the public you would then fall
under the requirement to open your code base if you are using GPL
code. The linksys routers use a lot of GPL code, so they were required
to release their entire source code publicly. However, if they only
linked to LGPL code they could still hide most of their source from
the public.
  LGPL code is fine for commercial deployment as long as it is somehow
separately linked to your code (at compile time or run time). Of
course, if you modify any of the LGPL code and you make some kind of
public release of a product that uses it, then you have to release the
LGPL source code that you changed. But even then, most of your code
can still be hidden from the public as long as the LGPL code can be
considered a separate body of code that was linked to your project.

I'm not a lawyer, but I think my statements are legally correct.

Eric