Need help understanding GNU LGPL terms

Question

I'm a new developer and recently have to work on project where I guess using arduino lib will be easy, because writing my own library will be a lot more time consuming. This isn't a mass production device, it is a embedded system that I have to develop to solve a task, my client will be using this system. The arduino lib which I'm using is licensed under GNU LGPL.

My question is:

1.Can I use the lib APIs in my code and then license my code under my own terms?

2.What is the deal with static linking and dynamic linking of this lib?

3.Do I have to redistribute my code or any object form of my code?

So far I don't see any need for me to modify the library code, will just be using APIs.

Answer 1

1.Can I use the lib APIs in my code and then license my code under my own terms?

Yes, as long as your license does not forbid users of the code/device to replace the LGPL library with a different version.

2.What is the deal with static linking and dynamic linking of this lib?

The LGPL requires that it must be possible to replace the LGPL code with a different (compatible) version and have a working executable using that code.

There are three ways of fulfilling that requirement

1. Using dynamic linking. Then the dynamic library (.so/.dll) can just be replaced.
2. Distribute object files of the application. This way, the new library can be relinked into the executable.
3. Distribute source code.

3.Do I have to redistribute my code or any object form of my code?

No, unless those files are needed to create a functioning executable that uses a new version of the LGPL library.

---

In the answers above, I have disregarded any contractual obligations you might have to provide your code to your client. The answers also apply to your client if they decide to sell the device to customers.