What practical steps shall I implement to redistribute log4cpp code with commercial project (win32) ?
As far as I understand I have to do at least following:
1. To place all the "core" log4cpp code into separate DLL.
2. in the "help/about" I shall place appropriate message about the fact that given product uses LGPL-licenced log4cpp product.
Anything else ?
Many thanks!
Igor.
P.S. Out of record: how great it would be if log4cpp would be under Apache or MIT X11 licence :)))
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Of course the COPYING file is authoritive here, but here are a few hints:
You must ensure that the recipients of your product receive or can get the source to log4cpp and that they can modify log4cpp and still use it with your product (e.g. for bug fixing). A DLL is the easiest solution for the latter.
For the former the recipient needs to know that your product uses log4cpp of course (and where to get it if you don't include the source code). The LGPL does not contain an obnoxious advertising clause so you're not obligated to put it in the 'help/about'. Placing it in the regular product document will suffice.
Also note that if you extend log4cpp, e.g. by deriving classes, you need to make available (in source) these extensions as well.
Good luck,
Bastiaan Bakker
PS. I don't want to discuss pros and cons of various licenses here, but I did not pick the LGPL out of the blue. It simply was in the best interest of log4cpps users, my employer and myself.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What practical steps shall I implement to redistribute log4cpp code with commercial project (win32) ?
As far as I understand I have to do at least following:
1. To place all the "core" log4cpp code into separate DLL.
2. in the "help/about" I shall place appropriate message about the fact that given product uses LGPL-licenced log4cpp product.
Anything else ?
Many thanks!
Igor.
P.S. Out of record: how great it would be if log4cpp would be under Apache or MIT X11 licence :)))
Hi Igor,
Of course the COPYING file is authoritive here, but here are a few hints:
You must ensure that the recipients of your product receive or can get the source to log4cpp and that they can modify log4cpp and still use it with your product (e.g. for bug fixing). A DLL is the easiest solution for the latter.
For the former the recipient needs to know that your product uses log4cpp of course (and where to get it if you don't include the source code). The LGPL does not contain an obnoxious advertising clause so you're not obligated to put it in the 'help/about'. Placing it in the regular product document will suffice.
Also note that if you extend log4cpp, e.g. by deriving classes, you need to make available (in source) these extensions as well.
Good luck,
Bastiaan Bakker
PS. I don't want to discuss pros and cons of various licenses here, but I did not pick the LGPL out of the blue. It simply was in the best interest of log4cpps users, my employer and myself.