Results 1 to 5 of 5

Thread: LGPL for QtUiTools.lib

  1. #1
    Join Date
    Feb 2010
    Posts
    99
    Thanks
    31
    Thanked 3 Times in 3 Posts
    Qt products
    Qt4
    Platforms
    MacOS X Unix/X11 Windows

    Default LGPL for QtUiTools.lib

    Hi,

    I am using QtUiTools.lib in an application that I am creating. I don't want to make my application open source, and use LGPL. But according to LGPL you cannot statically link to Qt libs, but in case of QtUiTools.lib, Qt doesn't provide the dll to QtUiTools. Can anyone tell me what are my options, other than buying license for Qt.

    Thanks

  2. #2
    Join Date
    Mar 2007
    Location
    Germany
    Posts
    229
    Thanks
    2
    Thanked 29 Times in 28 Posts
    Qt products
    Qt4
    Platforms
    Windows

    Default Re: LGPL for QtUiTools.lib

    I think there simply is no special dll for the UiTools. I also have an application that uses the QtUiTools and I deploy with Core, Gui and Xml.dll. I can imagine that the UiTools are part of the Gui.dll.

  3. #3
    Join Date
    Feb 2010
    Posts
    99
    Thanks
    31
    Thanked 3 Times in 3 Posts
    Qt products
    Qt4
    Platforms
    MacOS X Unix/X11 Windows

    Default Re: LGPL for QtUiTools.lib

    Yes there is no dll for UiTools. But I think that QtUiTools.lib gets statically linked with the application which violates the LGPL. That's why I am concerned.
    Thanks for update.

  4. #4
    Join Date
    Mar 2007
    Location
    Germany
    Posts
    229
    Thanks
    2
    Thanked 29 Times in 28 Posts
    Qt products
    Qt4
    Platforms
    Windows

    Default Re: LGPL for QtUiTools.lib

    I see no problem.
    You want the application to be licensed under LGPL. So you have to link dynamically and deploy the necessary dlls next to the executable. For an application using QtUiTools no additional dll is required. That's all

  5. #5

    Default Re: LGPL for QtUiTools.lib

    I am also interested in this issue. I believe that statically linking the QtUiTools.lib into a closed source application would be a violation of the LGPL. But, I wonder if it is possible to work around that by manually creating a shared library that consists only of QUiLoader. The quiloader.h header file would have to be modified to include the correct QT shared library export macros. I wonder if simply modifying the header file in this manner would violate the LGPL.

Similar Threads

  1. LGPL question
    By tim47 in forum Installation and Deployment
    Replies: 5
    Last Post: 15th March 2010, 09:07
  2. Qt GPL or LGPL Problem
    By zxvc in forum Qt-based Software
    Replies: 7
    Last Post: 11th March 2010, 10:55
  3. QtUiTools for WinCE ?
    By Gilles.Bordas in forum Installation and Deployment
    Replies: 1
    Last Post: 6th July 2008, 19:26
  4. Example QtUiTools linker error
    By phillies in forum Newbie
    Replies: 1
    Last Post: 26th June 2007, 22:27
  5. QtUiTools
    By drkbkr in forum Qt Programming
    Replies: 4
    Last Post: 13th July 2006, 16:29

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.