Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I want to use an LGPL-licensed library in my app for Microsoft's app marketplace. Is that OK?

share|improve this question
IANAL. The question is really do the terms of the MS App Marketplace and the LGPL conflict in any way? If the answer is "No" then it shouldn't be a problem. Otherwise it may be. Does the app marketplace prevent source distribution? Does the app marketplace forbid open source? Edit More info from a quick google of the problem:… – Thomas James Feb 13 '11 at 4:16
Also, keep in mind that you should NEVER EVER follow the legal advice that you get on the Internet, except if it comes from a lawyer. Preferably one who specializes in the given field, in this case: software licenses. So do take all these answers with a grain of salt, because otherwise you may be exposing yourself to lawsuits. – Radu Murzea Feb 3 '14 at 8:01
up vote 32 down vote accepted

Here is an encompassing answer:

In short: yes you can. But one important thing to take care of is that the GNU LGPL covered library is dynamically linked, not statically mixed with the main application.

It should also be possible to exchange that dynamically linked library for an independently compiled build. Otherwise you have likely intertwingled the library and main application code.

share|improve this answer
This is true for LGPL 2, but LGPL 3 seems to allow static linking if I understand it correctly. – Richard Le Mesurier Aug 14 '14 at 8:10
@mario, so is it also allowed on a closed-source app? Am I required to give credit? Anything? – Shimmy Apr 15 '15 at 20:37
@RichardLeMesurier, both versions permit static linking, but it's paramount to mention that software that statically links an LGPL library must be issued under an LGPL license itself, if I understand correctly. I am not a lawyer. This shall not be construed as legal advice. – Tyler Crompton Sep 21 '15 at 1:28
> it's paramount to mention that software that statically links an LGPL library must be issued under an LGPL license itself, if I understand correctly ===> Absolutely not. Any closed-source application can link statically with LGPL libs if it provides its object files to allow relinking with further / alternative versions of the LGPL library : – Jean-Michaël Celerier Apr 7 at 21:08
What happens with header-only LGPL libraries? – gnzlbg Jun 25 at 13:26

The LGPL license allows an application that references the binaries to remain closed-source. Also, there's nothing preventing you from selling an open source app on the Microsoft App Marketplace.

share|improve this answer

This article may help.

I suspect that because LGPL allows making the source code (of the library that you linked to) available via a download, it must be OK to use an LGPL-licensed lib in your app for Microsoft's marketplace.

Quote from LGPL version 2.1:

If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code.

The only thing that seems to be an issue is the "same place" requirement, which you will not be fulfilling if your app is being distributed via the marketplace.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.