Dynamic Libraries Link and Licenses

When building the external library project, I selected "Mach-O Type" as "Dynamic Library" and built it to create a framework file (folder).

And this framework file was imported and used in our app and distributed to the App Store.

Is this situation required to release the entire source code of our app under the LGPL 2.1 (or LGPL 3.0) license?

Enter file in the Mac command line and press Enter, “dynamically linked shared library” is displayed.

Replies

Is this situation required to release the entire source code of our app … ?

I recommend that you discuss this with your lawyer.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Is this situation required to release the entire source code of our app under the LGPL 2.1 (or LGPL 3.0) license?

No, that's not a requirement of the LGPL license.

But if the developers (wrongly) believe that it is a requirement of their license (even if it's not), they may take down your app (and maybe even your developer account) with a simple copyright notice. So it's not worth the headache.