Can I use an LGPL-2.1 library in proprietary software?
Last updated
TL;DR: Shipping a proprietary app that links the library: Yes. Shipping a modified copy of the library: Yes. LGPL-2.1 lets proprietary programs use the library, provided users can replace or relink the LGPL part and changes to the library itself stay LGPL.
Is shipping a proprietary app that links the library allowed under GNU Lesser General Public License v2.1 only?
Yes. Every use you described is granted by LGPL 2.1, and nothing you described is prohibited.
License: GNU Lesser General Public License v2.1 only (LGPL-2.1-only, curated)
Duties: attribution, license_notice, state_changes, share_alike, source_disclosure
Is shipping a modified copy of the library allowed under GNU Lesser General Public License v2.1 only?
Yes. Every use you described is granted by LGPL 2.1, and nothing you described is prohibited.
License: GNU Lesser General Public License v2.1 only (LGPL-2.1-only, curated)
Duties: attribution, license_notice, state_changes, share_alike, source_disclosure
What else should I know?
- Dynamic linking is the usual way to meet the relinking condition; static linking needs object files or an equivalent so users can relink.
What are the sources?
How can I check it myself (free, no key)?
{
"tool": "check_license",
"arguments": {
"license": "LGPL-2.1-only",
"intended_use": {
"commercial_use": true,
"redistribution": true
}
}
}Computed from a2ally's license profiles; not legal advice. JSON · Markdown
Get a free API key in one call
No card and no email needed. 100 free credits; the license and policy checks stay free without a key.
curl -s -X POST https://www.a2ally.com/v1/accounts/signup -H "Content-Type: application/json" -d '{"accept_terms":true}'
export A2ALLY_API_KEY=rs_... # the api_key from the reply (shown once)
curl -s https://www.a2ally.com/v1/licenses/check -H "Authorization: Bearer $A2ALLY_API_KEY" \
-H "Content-Type: application/json" -d '{"license":"MIT","intended_use":{"commercial_use":true}}'
