Re: [Opensync-users] May I modify libwbxml-0.11.0 source code to make it compile, and use it in commercial software

[Chris F. <cd...@fo...>]

On Mon, Nov 14, 2011 at 03:20:56PM +0800, Zeng,Weiming wrote:
> My question is related to LGPL licensing of libwbxml-0.11.0.
> 
> I got the source of libwbxml-0.11.0 but found it won't compile on Windows
> using Visual C++ 6 (missing wbxml_config.h). I'd like to modify the source
> and make it compile, then use it in the commercial software in a
> dynamic-link manner(DLL).  This proprietary is an email client with
> ActiveSync capability.
> 
> My concern is that as it's bounded by LGPL, may I keep the commercial
> software code proprietary, while using a modified libwbxml-0.11.0 ?

Yes, this is fine, since it is the LGPL involved, not the GPL.

If you use libwbxml as a DLL only, then yes, I don't think there is
any further burden on you.  As long as the end user has the ability to
replace that DLL with a new one of the same API, and have your software
work, that's fine.

If you use libwbxml in a static manner (linking it into the end EXE),
then you also need to provide the .obj files (not the source code) of
your proprietary program, so that the end user can replace the libwbxml
.obj file, and relink to create a new working EXE.

The basic goal being to preserve the usefulness of the libwbxml source
code in your final product, for your end uesr, so that he can modify it
freely, regardless of what it is linked to.

I'm not a lawyer, but I'm fairly sure about this. :-)  The FSF also has
FAQ's that may be of use to you.

Hope this helps,
- Chris