About licensing
About licensing
I would like to know about licensing my application written in C++ and using wxWidgets.
This is a close source commercial software. Should i get a license by paying fees or this is a free product for commercial development.
This is a close source commercial software. Should i get a license by paying fees or this is a free product for commercial development.
The wxWidgets license allows you to ship your code as closed source, and sell it. Basically what you can't do is make adjustments in the wxWidgets library and claim it your own. Other then that it is very flexible.
- Jorgen
- Jorgen
Forensic Software Engineer
Netherlands Forensic Insitute
http://english.forensischinstituut.nl/
-------------------------------------
Jorg's WasteBucket
http://www.xs4all.nl/~jorgb/wb
Netherlands Forensic Insitute
http://english.forensischinstituut.nl/
-------------------------------------
Jorg's WasteBucket
http://www.xs4all.nl/~jorgb/wb
-
- In need of some credit
- Posts: 2
- Joined: Fri Nov 05, 2010 11:58 am
So, concretly, it's the same as LGPL except that we are not forced to use the wxWidgets libraries dynamically to a DLL or SO file?
If so, does in this case we may use it statically within the closed source and is it mandatory to state in our licence files/documentations any mention that we are using wxWidgets (without bringing any modification to these libraries)?
Thanks in advance!
If so, does in this case we may use it statically within the closed source and is it mandatory to state in our licence files/documentations any mention that we are using wxWidgets (without bringing any modification to these libraries)?
Thanks in advance!
- tierra
- Site Admin
- Posts: 1355
- Joined: Sun Aug 29, 2004 7:14 pm
- Location: Salt Lake City, Utah, USA
- Contact:
Disclaimer: I am not a lawyer.
Correct, however, do note that this doesn't mean it's legal to also link GTK itself statically in your application too along with wxWidgets (in the case of using wxGTK), you still need to consider the licenses of any other libraries wxWidgets also depends on given the configuration you've chosen to use. This isn't typically something that requires much thought since wxWidgets has been careful to try to only depend on or include libraries compatible with the wxWindows License (i.e. expat, jpeg, libpng, libtiff, zlib, and tcl/tk regex code), but obviously GTK+ itself is a different story.silverkorn wrote:So, concretly, it's the same as LGPL except that we are not forced to use the wxWidgets libraries dynamically to a DLL or SO file?
The license does not require you to mention that you are using wxWidgets anywhere at all (though it would be nice if you did). Additionally, the license also allows you to even make modifications to the library without actually contributing the changes back to wxWidgets or making your source code for those changes available publicly at all either, however, it is still in your best interest if you do so since those improvements can be included in future releases of wxWidgets where you will no longer need to maintain your own set of patches you apply to wxWidgets every time you build your application against a new version.silverkorn wrote:If so, does in this case we may use it statically within the closed source and is it mandatory to state in our licence files/documentations any mention that we are using wxWidgets (without bringing any modification to these libraries)?
-
- In need of some credit
- Posts: 2
- Joined: Fri Nov 05, 2010 11:58 am
Re: About licensing
Thanks so much for so many informative stuff about licensing...so helpful
-
- In need of some credit
- Posts: 4
- Joined: Sat Jan 07, 2012 4:19 am
- Location: Brazil
Re:
But when we statically link an app with wxwidgets on linux, we are not statically linking with GTK, on the contrary, we will be dynamically linking with GTK, right?tierra wrote:Correct, however, do note that this doesn't mean it's legal to also link GTK itself statically in your application too along with wxWidgets (in the case of using wxGTK), you still need to consider the licenses of any other libraries wxWidgets also depends on given the configuration you've chosen to use. This isn't typically something that requires much thought since wxWidgets has been careful to try to only depend on or include libraries compatible with the wxWindows License (i.e. expat, jpeg, libpng, libtiff, zlib, and tcl/tk regex code), but obviously GTK+ itself is a different story.
Re: About licensing
Indeed linking against GTk statically is not common
"Keyboard not detected. Press F1 to continue"
-- Windows
-- Windows
-
- In need of some credit
- Posts: 1
- Joined: Tue Mar 13, 2012 7:04 pm
Re: About licensing
Forgive my ignorance, but when you say "closed source, and sell it. " does this mean i can actually relabel this as mine? Or do i have to disclose the source?
- tierra
- Site Admin
- Posts: 1355
- Joined: Sun Aug 29, 2004 7:14 pm
- Location: Salt Lake City, Utah, USA
- Contact:
Re: About licensing
They really meant in terms of an application built using wxWidgets.leslielane wrote:Forgive my ignorance, but when you say "closed source, and sell it. " does this mean i can actually relabel this as mine? Or do i have to disclose the source?
In the spirit of the license, it's open to allow redistribution of wxWidgets in binary form without the burden of distributing the source code along with it, sold with your application which is linked against it.
As far as actual legal boundaries, you really should talk with a lawyer.
Re: About licensing
Disclaimer : I'm not a lawyer. But I think the license forbids you from telling people that you made it all yourself. Now I don't believe the license requires you to put a huge "made with wxWidgets" label on itleslielane wrote:Forgive my ignorance, but when you say "closed source, and sell it. " does this mean i can actually relabel this as mine? Or do i have to disclose the source?
"Keyboard not detected. Press F1 to continue"
-- Windows
-- Windows