you ask them for the LGPL package, they send it to you, you compile ?
The onus is on the person making the app that links against the LGPL library to provide you with the build instruction.
At worse they would give you their main static library and Qt LGPL source code and you just have to relink them and open Xcode to upload it to your iDevice ?
I am not talking primarily about open source projects, but about closed source projects with LGPL components on app stores. You’d need the proprietary main object from them. Also, requiring that your users have an Apple dev account before they can execute their rights is problematic at best. I am not alone in rejecting Qt on these grounds, in favour of some MIT or similarly licensed alternative.
> I am not talking primarily about open source projects, but about closed source projects with LGPL components on app stores. You’d need the proprietary main object from them.
yes, and as I said if they are not providing them to you they are breaking the LGPL plain and simple. If they break their contract you're in undefined-behaviour land anyways :-)
> Also, requiring that your users have an Apple dev account before they can execute their rights is problematic at best. I am not alone in rejecting Qt on these grounds, in favour of some MIT or similarly licensed alternative.
You don't need a dev account to upload something to your phone since Xcode 7 or 8. Only to put it on the appstore. Prior to that, sure, it was hard to comply with the LGPL.