Topics created by ksitu

@tom we can try that in a little bit and get back to you

This is not legal advice, but Wikipedia has a nice writeup on LGPL that may be relevant to your question

https://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License

"Whether a work that uses an LGPL program is a derivative work or not is a legal issue. A standalone executable that dynamically links to a library through a .so, .dll, or similar medium is generally accepted as not being a derivative work as defined by the LGPL. It would fall under the definition of a "work that uses the Library". Paragraph 5 of the LGPL version 2.1 states:

A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License.

Essentially, if it is a "work that uses the library", then it must be possible for the software to be linked with a newer version of the LGPL-covered program. The most commonly used method for doing so is to use "a suitable shared library mechanism for linking". Alternatively, a statically linked library is allowed if either source code or linkable object files are provided."

Hi,

The MV library is made by qualcomm and has some licenses attached to it, we can't publish (and don't even have access to ourselves) the source code and have to keep the headers behind a EULA. Since both our voxl system images and docker build environments are behind said EULA, that's where we keep the header. It can be found in /usr/include/mv/ on both the voxl and the voxl-emulator docker image.