Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Reg: Licencing software
Forum Updated to NodeBB v4.3 + New Features

Reg: Licencing software

Scheduled Pinned Locked Moved General and Desktop
5 Posts 3 Posters 1.8k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    madhuti
    wrote on last edited by
    #1

    Hi,

    My requirement is like, i am planning to develop an commercial application using "Opensource QT".
    So, what are the things i need to take care.

    1. license of my software.
    2. should i have to get a "licenced QT" or still i can use the opensource for free.

    Thanks in advance,
    Madhu

    1 Reply Last reply
    0
    • S Offline
      S Offline
      Skylar
      wrote on last edited by
      #2

      Hi,

      You can use the LGSL license if you need for this.

      Having the commercial license with gice you some advantages or not based on your target development.

      http://qt.nokia.com/products/licensing

      In most cases, the bug is mine. But of the remaining lines are correct.

      1 Reply Last reply
      0
      • S Offline
        S Offline
        Skylar
        wrote on last edited by
        #3

        Check the QT Commercialpage about why.

        http://www.digia.com/en/Qt/Try-Qt-Now/

        In most cases, the bug is mine. But of the remaining lines are correct.

        1 Reply Last reply
        0
        • I Offline
          I Offline
          ivan
          wrote on last edited by
          #4

          If you choose LGPL:

          If you statically link Qt to your application, you need to release all the code under LGPL.
          If you link your application dynamically to Qt, and haven't patched Qt, you don't need to release your code under any free/open source license.
          If you link your application dynamically to Qt, and are distributing a patched version of Qt, you need to provide those patches under LGPL. The rest of the code in your application can stay proprietary/closed.

          Ivan Čukić | ivan.cukic(at)kde.org | KDE e.V.
          Qt Ambassador (from the old Nokia days)

          1 Reply Last reply
          0
          • M Offline
            M Offline
            madhuti
            wrote on last edited by
            #5

            Thank you Ivan and Skylar. You have given me a valuable info.

            1 Reply Last reply
            0

            • Login

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Users
            • Groups
            • Search
            • Get Qt Extensions
            • Unsolved