Qt pricing (most up to date) [closed]

Question

Closed. This question is off-topic. It is not currently accepting answers.

---

Want to improve this question? Update the question so it's on-topic for Stack Overflow.

Closed 9 years ago.

Improve this question

I am thinking about using QT for rich GUI commercial multiplatform programs. A would want to know how much the commercial license would cost.

I found just old prices (2008): https://stackoverflow.com/questions/352896/qt-commercial-licenses

1. I am interested for the actual price (even earlier to see how it rises) for: win+osx

2. The license is one time or I have to buy license yearly?

3. Is there anyone who uses the LGPL version commercially? (I know that it can be done but I might need to make changes to QT without releasing the code for it: https://stackoverflow.com/questions/2945612/qt-lgpl-licencing-for-a-free-application-with-closed-source)

4. Actually this price policy (We don't tell you the price! We will call you!) is really strange to me, should I rather stay away form QT? I just tried it (15-20 hours) so going with other technology (.Net and just for Windows by dropping multiplatform support) is still an option

Answer 1

I'm no lawyer, so I'm not an expert in this area. I just wanted to point out that you can still develop closed-source software using an LGPL license. The catch is that you can't edit the Qt libraries without releasing the changes under LGPL.

Related SO thread: https://stackoverflow.com/questions/94346/can-i-legally-incorporate-gpl-lgpl-open-sourced-software-in-a-proprietary-cl. Read the top answer to that question, there is a much better explanation there.

Unfortunately I can't help you with the pricing, but if you're not altering Qt itself then you may not need to pay for it at all.

Answer 2

I have used Qt LGPL in commercial closed source applications. Besides the minor inconvenience of dynamic linking, I see no reason not to.

Your concern in bullet 3:

I know that it can be done but I might need to make changes to QT without releasing the code for it

This is a very strange requirement. I don't know why you would want to hack on the Qt source, and then not release your changes to it. If you're comparing it to .Net, consider you wouldn't be able to make changes to that framework at all.