wxWidgets Discussion Forum

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

Its packaged with wxWidgets, and yes you can.

http://www.opensource.org/licenses/wxwindows.php

But I think I have to redistribute my app under the GPL if I use wxWindows... Is that right?

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/

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

Did I really understand it? The binary version of an app doesn't have to be published under the GPL? This is really cool!

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

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.

Check out the wiki page about this -
http://wiki.wxwidgets.org/wiki.pl?Distr ... plications

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?

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?

Nope - that's LGPL.

Ah ok

Thanks