opensync-users

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

[Zeng,Weiming <hi...@gm...>]

Hi,

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 ?

My modification is just to make it compile, but not to modify the internal
of libwbxml.

Is this a case prohibited by LGPL, a close source commercial software dynamic
links to a modified version of LGPL software?

Thanks!

*Weiming*

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

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

[Zeng,Weiming <hi...@gm...>]

Hi Chris, thank you for your reply!

In this case, may I distribute my compiled libwbxml-0.11.0 DLL file along
with the proprietary email client? Or should I make it a separate package
to deliver?

- Weiming

On Mon, Nov 14, 2011 at 3:51 PM, Chris Frey <cd...@fo...> wrote:

> 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
>
>
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users
>

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 04:23:43PM +0800, Zeng,Weiming wrote:
> In this case, may I distribute my compiled libwbxml-0.11.0 DLL file along
> with the proprietary email client? Or should I make it a separate package
> to deliver?

I think either is suitable, but remember that you need to make the source
available for the library.  So probably the path of least headache is
to just include both the DLL and the source inside your Windows installer.

That way, the user always has both, right from the start.

- Chris

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

[Zeng,Weiming <hi...@gm...>]

 Thank you very much for your help!
I'll choose to include both the DLL and its source code inside the email
client installer.

Best regards,
- Weiming

On Mon, Nov 14, 2011 at 7:14 PM, Chris Frey <cd...@fo...> wrote:

> On Mon, Nov 14, 2011 at 04:23:43PM +0800, Zeng,Weiming wrote:
> > In this case, may I distribute my compiled libwbxml-0.11.0 DLL file along
> > with the proprietary email client? Or should I make it a separate package
> > to deliver?
>
> I think either is suitable, but remember that you need to make the source
> available for the library.  So probably the path of least headache is
> to just include both the DLL and the source inside your Windows installer.
>
> That way, the user always has both, right from the start.
>
> - Chris
>
>
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users
>

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

[Zeng,Weiming <hi...@gm...>]

Hi Adrià, thank you for your advise. Yes the win32 project of libwbxml has
been ignored by the author for a long time.

- Weiming

2011/11/14 Adrià Cereto Massagué <sso...@gm...>

> AFAIT, you may do so as long as you make the modified libwbxml available.
> Better yet, you could send back your modificacions to the original
> author(s) or current maintainers.
> El 14/11/2011 08:21, "Zeng,Weiming" <hi...@gm...> escribió:
>
>>  Hi,
>>
>> 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 ?
>>
>> My modification is just to make it compile, but not to modify the
>> internal of libwbxml.
>>
>> Is this a case prohibited by LGPL, a close source commercial software dynamic
>> links to a modified version of LGPL software?
>>
>> Thanks!
>>
>> *Weiming*
>>
>>
>> ------------------------------------------------------------------------------
>> RSA(R) Conference 2012
>> Save $700 by Nov 18
>> Register now
>> http://p.sf.net/sfu/rsa-sfdev2dev1
>> _______________________________________________
>> Opensync-users mailing list
>> Ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/opensync-users
>>
>>

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

[Michael B. <mic...@cm...>]

Hi,

the missing wbxml_config.h is usually a result of a missing cmake run. I
don't use MS Windows. So I can just apply patches from Windows
users/developers.

Actually there is no active ticket which reports a missing file.

I never touched the stuff in the directory win32/. So I don't know if I
can simply remove the directory or if I have to repair it.

Best regards

Michael

P.S. Sorry for my very late response but libwbxml is today just a hobby.

Am 11/14/11 08:20, schrieb Zeng,Weiming:
> Hi,
> 
> 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 ?
> 
> My modification is just to make it compile, but not to modify the
> internal of libwbxml.
> 
> Is this a case prohibited by LGPL, a close source commercial software
> dynamic links to a modified version of LGPL software?
> 
> Thanks!
> 
> /Weiming/
> 
> 
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> 
> 
> 
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users


-- 
___________________________________________________________________

Michael Bell                        Humboldt-Universitaet zu Berlin

Tel.: +49 (0)30-2093 70143          ZE Computer- und Medienservice
Fax:  +49 (0)30-2093 70135          Unter den Linden 6
mic...@cm...       D-10099 Berlin
___________________________________________________________________

PGP Fingerprint: 09E4 3D29 4156 2774 0F2C  C643 D8BD 1918 2030 5AAB