Can I include an LGPL library in an MPL licensed project?

Question

I have a project, php based, thats licensed under the MPL (not a trilicense, and it can't be changed without more work than I'd like to put into a non-development task).

I want to include an LGPL licensed library. I'm going to be dumping it in directly- any patches I make I will be sending back to the main project. I know that including MPL code in an LGPL project is problematic, but I think it should work the other way around.

Am I right, can I use an LGPL licensed library inside an MPL licensed project?

Clarification -

I mean the Mozilla Public License, not the microsoft one.

By inside I mean this library (as well as others like it) would be put in a directory named "third_party" and copied wholesale into that directory. From there we'd include them and use them as needed.

Answer 1

What do you mean with inside? And do you mean the Mozilla or Microsoft Public License? Either way, you're allowed to use LGPL even with closed source, as long as you just link against the static binary.

With the LGPL you're allowed to:

• Use the code in any OpenSource Project as long the license it compatible with the LGPL (would be GPL, AGPL f.e.)
• Link against the code (f.e. LGPL Project compiled into a DLL and then referenced) in any kind of project, even closed source.

Edit: As I just figured out, the Mozilla Public License is incompatible with the GPL, meaning you're most likely left with linking the LGPL code.

Edit 2: You're not allowed to include any code into your app, but you're allowed to link against the compiled LGPL assembly. Meaning you put the ready-to-use LGPL binary into that ThirdParty folder, and work with that one.