GNU LGPL and other related questions

[amleto]

look at it this way - it doesnt matter how you use that helper app, it is going to get used in your app, or by your app one way or another. As part of the contract, that helper app code is necessarily going to be included.

LGPL requires that your thing be rebuildable with a different version of the library licensed with lgpl. So no, lgpl never requires you to release *source code* (unless you modified the library). Due to the terms of the contract, the code will still have to be released, though so not sure what the point in your question is.

[wysota]

First of all, LGPL is not a "transient" licenese (as opposed to e.g. GPL) -- using a LGPL component doesn't enforce anything on your app. You are only obligated to make sure the licence of the LGPL component is satisfied (which indirectly might enforce some limitations on your program). Also note that licenses such as GPL and LGPL are focused on what happens if you distribute the component in question. If using your helper app with the main app is optional then you are not in any way forced to release neither the binary nor the source code of your helper app. If the helper app is required for the main app to work (regardless how the technical side of using it looks like) then it counts as part of the project and you should hand it over to the client.

[mtnbiker66]

The point of my question was if my helper code had to be included per LGPL (ignoring any contract with the client) -- if no, then I was going to have my code just call either the help app as a .exe via QProcess or a library. If I need to include the code from it I may as well fold the code into my project and make one deliverable...

Thanks!

Kodi

---

Added after 5 minutes:

Yep, it's going to be required by my app so that answers the original question (and is what I pretty much thought would be the case and was hoping to not be), but now I'll have to decide whether to fold the code into mine, or deliver a .exe/library and deliver two sets of code in the end...Probably should do the former, but I have symbols(s) not found errors

Thanks, all!

[ChrisW67]

I am still unsure exactly which components of the end system are covered by the LGPL.

As far as I can see your application is a the subject of the contract and all the source belongs to the client. This has nothing to do with the LGPL.

Your friend's application is closed source, also nothing to do with the LGPL. Whether you have to deliver the source to your client depends very strongly on the scope of the contract you have and what the client already has. For example, if they already licence your friend's application in binary form and your application only calls that pre-existing program (using QProcess) then your friend's program is not your problem.

As with all contractual issues please seek professional legal advice.