Results 1 to 3 of 3

Thread: Mac OS X and QT LGPL licensing (dynamically linked libraries)

  1. #1
    Join Date
    Dec 2009
    Posts
    1
    Qt products
    Qt4
    Platforms
    MacOS X Windows

    Question Mac OS X and QT LGPL licensing (dynamically linked libraries)

    Hi,

    I'm totally new to C++ and QT having used REALBasic for application development (I'm a web developer at heart).

    Qt looks good but I'm a little confused about the licensing and use of dynamically linked libraries.

    If I were to develop with Qt (but not change and re-use Qt's source code), can I deploy a proprietary application (with a price tag) and not make public its source code?

    More specifically, I understand you need to dynamically like Qt's libraries in your deployed - which I assume is the normal use of includes.

    If I were to deploy an application on OS X using the macdeployqt, whereby it automatically bundles the Qt libraries within the .app package/folder, is that still dynamic linking of the libraries and therefore within the LGPL license requirements (assuming I haven't used other external code that would be outside the LGPL)?

    Any help would be appreciated before I dive-in.

  2. #2
    Join Date
    Jan 2006
    Location
    Germany
    Posts
    4,380
    Thanks
    19
    Thanked 1,005 Times in 913 Posts
    Qt products
    Qt4
    Platforms
    Unix/X11 Windows Symbian S60
    Wiki edits
    5

    Default Re: Mac OS X and QT LGPL licensing (dynamically linked libraries)

    Quote Originally Posted by ubernick View Post
    If I were to develop with Qt (but not change and re-use Qt's source code), can I deploy a proprietary application (with a price tag) and not make public its source code?
    Yes.

    More specifically, I understand you need to dynamically like Qt's libraries in your deployed - which I assume is the normal use of includes.

    If I were to deploy an application on OS X using the macdeployqt, whereby it automatically bundles the Qt libraries within the .app package/folder, is that still dynamic linking of the libraries and therefore within the LGPL license requirements (assuming I haven't used other external code that would be outside the LGPL)?
    It's no problem. You application is still dynamically linked. It's just like you would make a zip package.

  3. #3
    Join Date
    Sep 2009
    Location
    Finland
    Posts
    63
    Thanks
    1
    Thanked 22 Times in 19 Posts
    Qt products
    Qt4 Qt/Embedded
    Platforms
    Unix/X11 Windows Symbian S60

    Default Re: Mac OS X and QT LGPL licensing (dynamically linked libraries)

    Please take a look at this:
    Qt: Making the right licensing decision

Similar Threads

  1. Another question to clarify licensing under LGPL.
    By Alex_123 in forum General Discussion
    Replies: 3
    Last Post: 20th October 2009, 18:31
  2. How can we use dynamically linked lib in QT?
    By learning_qt in forum Qt Programming
    Replies: 3
    Last Post: 16th December 2008, 14:04

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Digia, Qt and their respective logos are trademarks of Digia Plc in Finland and/or other countries worldwide.