Selling apps using wxWindows
-
- Experienced Solver
- Posts: 51
- Joined: Sun Sep 12, 2004 11:58 am
- Location: Hamburg, Germany
- Contact:
Selling apps using wxWindows
Hi!
As I like wxWindows very much, I'd like to use it for commercial projects, too. Where can I find the license? I'd like to know if it is possible to sell apps using wxWindows...
Thanks,
Andi
As I like wxWindows very much, I'd like to use it for commercial projects, too. Where can I find the license? I'd like to know if it is possible to sell apps using wxWindows...
Thanks,
Andi
No.
http://www.wxwidgets.org/newlicen.htm
"The wxWidgets 2 licence is essentially the L-GPL (Library General Public Licence), with an exception stating that derived works in binary form may be distributed on the user's own terms. This is a solution that satisfies those who wish to produce GPL'ed software using wxWidgets, and also those producing proprietary software."
There's a few examples such us Dialog Blocks.
http://www.anthemion.co.uk/dialogblocks/
http://www.wxwidgets.org/newlicen.htm
"The wxWidgets 2 licence is essentially the L-GPL (Library General Public Licence), with an exception stating that derived works in binary form may be distributed on the user's own terms. This is a solution that satisfies those who wish to produce GPL'ed software using wxWidgets, and also those producing proprietary software."
There's a few examples such us Dialog Blocks.
http://www.anthemion.co.uk/dialogblocks/
...
-
- Knows some wx things
- Posts: 31
- Joined: Fri Sep 10, 2004 1:03 pm
- Location: Troy, NY
- Contact:
Exactly. This is one of many cool aspects of wxWidgets. QT windows windows licencing scheme is precisely what drew me to wxWidgets.
eros wrote: "The wxWidgets 2 licence is essentially the L-GPL (Library General Public Licence), with an exception stating that derived works in binary form may be distributed on the user's own terms. This is a solution that satisfies those who wish to produce GPL'ed software using wxWidgets, and also those producing proprietary software."
You need to be really thourough with licensing. You can start at this link
http://www.wxwindows.org/newlicen.htm
You should also get yourself familiar with GPL and Lesser GPL (many links):
http://www.gnu.org/licenses/licenses.html
CG
http://www.wxwindows.org/newlicen.htm
You should also get yourself familiar with GPL and Lesser GPL (many links):
http://www.gnu.org/licenses/licenses.html
CG
What I understand is, if you statically link against an GPL'd library then you have to make your source available. On linux for example you are going to have to check every library along the way to make sure you are not statically linking against a GPL'd library.
Unless I have it all backwards...
CG
Unless I have it all backwards...
CG
I looked at wx and found where this was mentioned: docs/readme.txt
Snip:
However, if you distribute wxGTK or wxMotif (with Lesstif) version
of your application, don't forget that it is linked against
GTK+ (or Lesstif) which is covered by LGPL *without* exception
notice. Under Linux systems your app is probably linked
against LGPL glibc as well. Please read carefully LGPL, section 6.
which describes conditions for distribution of closed source applications
linked against LGPL library. Basically you should link dynamically and
include source code of LGPL libraries with your product (unless it is
already present in user's system - like glibc usually is).
If compiled with --enable-odbc (Unix only), wxWidgets library will
contain iODBC library which is covered by LGPL.
Snip:
However, if you distribute wxGTK or wxMotif (with Lesstif) version
of your application, don't forget that it is linked against
GTK+ (or Lesstif) which is covered by LGPL *without* exception
notice. Under Linux systems your app is probably linked
against LGPL glibc as well. Please read carefully LGPL, section 6.
which describes conditions for distribution of closed source applications
linked against LGPL library. Basically you should link dynamically and
include source code of LGPL libraries with your product (unless it is
already present in user's system - like glibc usually is).
If compiled with --enable-odbc (Unix only), wxWidgets library will
contain iODBC library which is covered by LGPL.
- Ryan Norton
- wxWorld Domination!
- Posts: 1319
- Joined: Mon Aug 30, 2004 6:01 pm
Check out the wiki page about this -
http://wiki.wxwidgets.org/wiki.pl?Distr ... plications
http://wiki.wxwidgets.org/wiki.pl?Distr ... plications
[Mostly retired moderator, still check in to clean up some stuff]
On a sidenote... If you use GPL code, you do not have to release your source (as far as I can understand). You only have to release your bytecode (.obj-files in VisualC, .o in GCC-compilers), so that the end-people who want to compile it against another version of the library, will be able to do that. Or is that the lesser GPL-thing?
wxWidgets: SVN/trunk
OS: WinXP/2 + Ubuntu + Mac 10.4.11
Compiler: VS2005 + GCC 4.2 + GCC 4.0.1
-----
home: http://www.salvania.be
OS: WinXP/2 + Ubuntu + Mac 10.4.11
Compiler: VS2005 + GCC 4.2 + GCC 4.0.1
-----
home: http://www.salvania.be
- Ryan Norton
- wxWorld Domination!
- Posts: 1319
- Joined: Mon Aug 30, 2004 6:01 pm
Nope - that's LGPL.KaReL wrote:On a sidenote... If you use GPL code, you do not have to release your source (as far as I can understand). You only have to release your bytecode (.obj-files in VisualC, .o in GCC-compilers), so that the end-people who want to compile it against another version of the library, will be able to do that. Or is that the lesser GPL-thing?
[Mostly retired moderator, still check in to clean up some stuff]
Ah ok
Thanks
Thanks
wxWidgets: SVN/trunk
OS: WinXP/2 + Ubuntu + Mac 10.4.11
Compiler: VS2005 + GCC 4.2 + GCC 4.0.1
-----
home: http://www.salvania.be
OS: WinXP/2 + Ubuntu + Mac 10.4.11
Compiler: VS2005 + GCC 4.2 + GCC 4.0.1
-----
home: http://www.salvania.be