Results 1 to 20 of 24

Thread: Things to inlcude in an LGPL distribution

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Join Date
    Dec 2010
    Posts
    34
    Thanks
    10
    Qt products
    Qt4
    Platforms
    MacOS X Windows

    Default Re: Things to inlcude in an LGPL distribution

    Quote Originally Posted by Lykurg View Post
    By simply replacing the Qt dll's with his own/modified ones.
    Oh, that simple

  2. #2
    Join Date
    Sep 2009
    Location
    UK
    Posts
    2,447
    Thanks
    6
    Thanked 348 Times in 333 Posts
    Qt products
    Qt4
    Platforms
    Windows

    Default Re: Things to inlcude in an LGPL distribution

    The object files would only be needed if you statically linked, then its upto them how to relink them to create a new executable. No one will bother, but at least you complied with the license by giving them the option.

    Of course, object files are not necessary (even legally) for dynamically linked builds as you can just change the DLL.

  3. #3
    Join Date
    Dec 2010
    Posts
    34
    Thanks
    10
    Qt products
    Qt4
    Platforms
    MacOS X Windows

    Default Re: Things to inlcude in an LGPL distribution

    Thanks once again guys.

    Not that I plan on moving to MS Visual Studio, but how does anyone know how the licensing works with applications developed with that? Is it the same as with the commercial license of QT?

  4. #4
    Join Date
    Jan 2006
    Location
    Warsaw, Poland
    Posts
    33,359
    Thanks
    3
    Thanked 5,015 Times in 4,792 Posts
    Qt products
    Qt3 Qt4 Qt5 Qt/Embedded
    Platforms
    Unix/X11 Windows Android Maemo/MeeGo
    Wiki edits
    10

    Default Re: Things to inlcude in an LGPL distribution

    A licence is a licence. It doesn't matter what tools you use. LGPL doesn't care. It only says about redistributing the licenced component.
    Your biological and technological distinctiveness will be added to our own. Resistance is futile.

    Please ask Qt related questions on the forum and not using private messages or visitor messages.


  5. #5
    Join Date
    Dec 2010
    Posts
    34
    Thanks
    10
    Qt products
    Qt4
    Platforms
    MacOS X Windows

    Default Re: Things to inlcude in an LGPL distribution

    I was just thinking about 'what' libraries are actually 'QT' libraries. The libraries in my project are:

    libgcc_s_dw2-1.dll
    mingwm10.dll
    QtCore4.dll
    QtGui4.dll

    I assume that the QT libraries are definitely part of the LGPL licence, but are the mingw and libgcc ones? They all came out of the QT installation folder...

  6. #6
    Join Date
    Jan 2006
    Location
    Warsaw, Poland
    Posts
    33,359
    Thanks
    3
    Thanked 5,015 Times in 4,792 Posts
    Qt products
    Qt3 Qt4 Qt5 Qt/Embedded
    Platforms
    Unix/X11 Windows Android Maemo/MeeGo
    Wiki edits
    10

    Default Re: Things to inlcude in an LGPL distribution

    Quote Originally Posted by The physicist View Post
    libgcc_s_dw2-1.dll
    mingwm10.dll

    I assume that the QT libraries are definitely part of the LGPL licence, but are the mingw and libgcc ones? They all came out of the QT installation folder...
    http://www.mingw.org/license
    These are the "MinGW runtime".
    Your biological and technological distinctiveness will be added to our own. Resistance is futile.

    Please ask Qt related questions on the forum and not using private messages or visitor messages.


  7. The following user says thank you to wysota for this useful post:

    The physicist (10th January 2011)

  8. #7
    Join Date
    Dec 2010
    Posts
    34
    Thanks
    10
    Qt products
    Qt4
    Platforms
    MacOS X Windows

    Default Re: Things to inlcude in an LGPL distribution

    The MinGW base runtime package has been placed in the public domain, and is not governed by copyright. This basically means that you can do what you like with the code.
    I couldn't find an explicit list of the dlls that belong to MinGW runtime, but the above licensing statement is pretty flexible!

  9. #8
    Join Date
    Jan 2006
    Location
    Warsaw, Poland
    Posts
    33,359
    Thanks
    3
    Thanked 5,015 Times in 4,792 Posts
    Qt products
    Qt3 Qt4 Qt5 Qt/Embedded
    Platforms
    Unix/X11 Windows Android Maemo/MeeGo
    Wiki edits
    10

    Default Re: Things to inlcude in an LGPL distribution

    mingwm10.dll is the runtime. libgcc_s_dw2-1.dll probably falls under the same licence GCC does (which I think is LGPL) but it's possible it's part of the runtime too.
    Your biological and technological distinctiveness will be added to our own. Resistance is futile.

    Please ask Qt related questions on the forum and not using private messages or visitor messages.


  10. #9
    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: Things to inlcude in an LGPL distribution

    Only QtCore4.dll and QtGui4.dll are Qt libraries, and thereof LGPL. The others are from mingw. They have their own license.
    But as far as I know you can deploy them (unchanged) freely without any restrictions.

    EDIT: Uh, there was a second page...

Similar Threads

  1. Distribution and license LGPL
    By skuallpa in forum Installation and Deployment
    Replies: 1
    Last Post: 15th October 2010, 08:08
  2. Q_DECLARE_PUBLIC and other things I dont understand ?
    By tonnot in forum Qt Programming
    Replies: 1
    Last Post: 6th October 2010, 11:03
  3. Replies: 4
    Last Post: 13th June 2010, 12:31
  4. Replies: 4
    Last Post: 10th March 2007, 04:28
  5. Replies: 2
    Last Post: 14th February 2006, 15:28

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.