AForge.NET

  :: AForge.NET Framework :: Articles :: Forums ::

merge assemblies and LGPL

Forum to discuss the AForge.NET project itself (not Framework), its news, events, articles, etc.

merge assemblies and LGPL

Postby squid » Mon Jul 26, 2010 12:28 pm

Hi

Can I use ILMerge to merge some assemblies in one assembly? Is it OK for LGPL license? I want to did it for easy usage and deployment.

Thank you!
squid
 
Posts: 5
Joined: Mon Jul 26, 2010 12:25 pm

Re: merge assemblies and LGPL

Postby andrew.kirillov » Mon Jul 26, 2010 1:37 pm

Hello,

Your question is answered in chapter 4.d.0 of LGPL license:
"Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source."

For your case the above means, that you also should provide (in some way) all the other assemblies (other components plus your assemblies), so user could reproduce the product you've developed in the case if new version of the component (AForge.NET framework, for example) is released. Not really sure it simplifies deployment a lot.

Or you may go to 4.d.1 chapter, which says using shared libraries as they are.

As for me (if I needed doing something like this), I would use ILMerge for all the assemblies I've developed, but keep the rest 3rd party components as they are.


Also don't forget chapter 4.c ;) :
"For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document."
With best regards,
Andrew


Interested in supporting AForge.NET Framework?
User avatar
andrew.kirillov
Site Admin, AForge.NET Developer
 
Posts: 3439
Joined: Fri Jan 23, 2009 9:12 am
Location: UK

Re: merge assemblies and LGPL

Postby squid » Mon Jul 26, 2010 1:45 pm

yay, don't love LGPL :lol:

ok, i'll use unchanged dlls in additional folder + place a copy of license to folder + link to this website + words about library in license in help file.

all correct?
squid
 
Posts: 5
Joined: Mon Jul 26, 2010 12:25 pm

Re: merge assemblies and LGPL

Postby andrew.kirillov » Mon Jul 26, 2010 1:56 pm

Should be fine
With best regards,
Andrew


Interested in supporting AForge.NET Framework?
User avatar
andrew.kirillov
Site Admin, AForge.NET Developer
 
Posts: 3439
Joined: Fri Jan 23, 2009 9:12 am
Location: UK

Re: merge assemblies and LGPL

Postby squid » Tue Jul 27, 2010 3:52 pm

Well, we still planned to use merged version, and have an independent builds for FW 2.0 and 4.0.

SO,

unchanged dlls in additional folder + place a copy of license to folder + link to this website + words about library in license in help file + .bat file that allow 3rd-party users to create a build will be ok?
squid
 
Posts: 5
Joined: Mon Jul 26, 2010 12:25 pm

Re: merge assemblies and LGPL

Postby andrew.kirillov » Tue Jul 27, 2010 9:47 pm

squid wrote:unchanged dlls in additional folder + place a copy of license to folder + link to this website + words about library in license in help file + .bat file that allow 3rd-party users to create a build will be ok?

Yes, if it allows to build your end result (product you distribute). I am not picky, it is just LGPL ;)
With best regards,
Andrew


Interested in supporting AForge.NET Framework?
User avatar
andrew.kirillov
Site Admin, AForge.NET Developer
 
Posts: 3439
Joined: Fri Jan 23, 2009 9:12 am
Location: UK

Re: merge assemblies and LGPL

Postby squid » Wed Jul 28, 2010 8:55 am

But I do not need to open my product source using this way, correct?
squid
 
Posts: 5
Joined: Mon Jul 26, 2010 12:25 pm

Re: merge assemblies and LGPL

Postby andrew.kirillov » Wed Jul 28, 2010 9:07 am

No, you don't need to open :) If you do changes to LGPL components, then you need to open those changes. But not the code of your product.

All is written in LGPL text - you are welcome to read it ;)
With best regards,
Andrew


Interested in supporting AForge.NET Framework?
User avatar
andrew.kirillov
Site Admin, AForge.NET Developer
 
Posts: 3439
Joined: Fri Jan 23, 2009 9:12 am
Location: UK

Re: merge assemblies and LGPL

Postby squid » Wed Jul 28, 2010 9:22 am

Hi

Sorry, Andrew, lawers documents its not for my braing....

Thank you for your perfect product!
squid
 
Posts: 5
Joined: Mon Jul 26, 2010 12:25 pm




Return to AForge.NET