Chronological Thread 

< Chronological >      < Thread >

---

Hi,

Trying to get my head around the LGPL and what it means if we wanted to
use sctp-1.0.3. Our project is an embedded application, where we build for
an embedded processor on a custom board. So far we don't have any LGPL
bits in our software. The executable object can only be run on our
architecture.

So I'm assuming that we come under the category of `work based on the
library'.

Am I reading the LGPL correctly in saying that we can use sctp-1.0.3 and
link it to our target as long as we promise for 3 years to provide the
source code of all changes we make to sctp and proved all the other
objects required to link our proprietary target ? Is that our simplest way
to obey the LGPL and not have to release our oodles of source code (which
could never happen).

thanks,
davidp.
--
David Pascoe,
mailto:dp AT ii.net,
Western Australia

"The use of COBOL cripples the mind; its teaching should, therefore, be
regarded as a criminal offense". -- E. W. Dijkstra

---

• [SCTP-Discussion] sctp under LGPL for embedded application, David Pascoe, 08/18/2005
  • Re: [SCTP-Discussion] sctp under LGPL for embedded application, Michael Tuexen, 08/19/2005
    • Re: [SCTP-Discussion] sctp under LGPL for embedded application, dp, 08/19/2005
      • Re: [SCTP-Discussion] sctp under LGPL for embedded application, Michael Tuexen, 08/19/2005

---

Archive powered by MHonArc 2.6.19+.