LGPL/MPL and static libraries [closed]

Question

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.

---

Want to improve this question? Update the question so it's on-topic for Stack Overflow.

Closed 5 years ago.

Improve this question

I need to compile LGPL licensed code into a proprietary static iOS library. Since the code is used in static library I can't link against a precompiled version of the LGPL licensed library.

How do I go about this, and what do I have to release if I compile it into my lib? I obviously can't release the (whole) proprietary source.

The specific library I am talking about is libical which is licensed under LGPL 2.1 or MPL 1.0.

Answer 1

Prefacing this with the usual IANAL:

Depends on the version of the LGPL it's using. If version 2, you do not need to supply your source code until asked for it. That's the way the license is written. However, when it's asked for, you will need to provide it via some easily accessible medium.

If it's LGPLv3, my suggestion is to find another library. The GPLv3 family of licenses are not compatible with AppStore distribution at all.

Answer 2

The LGPL license says you need to provide three bits:

1. The LGPL source-code as used in your product.
2. The object-files of your proprietary code
3. A tool to build the source-code and link it with the object-files, resulting in the very same product you submitted to Appstore.

It is tedious and complicated, but very doable.