Results 1 to 7 of 7

Thread: Static vs. Dynamic Building for GPL Open Source Software Release

  1. #1
    Join Date
    Feb 2008
    Location
    Riverside, CA
    Posts
    18
    Thanks
    4
    Qt products
    Qt4
    Platforms
    Unix/X11 Windows

    Default Static vs. Dynamic Building for GPL Open Source Software Release

    Is there any legal issue with statically linking the QT libraries for a GPL OSS release? Or does it have to be dynamic for compliance purposes?

  2. #2
    Join Date
    Jan 2006
    Location
    Warsaw, Poland
    Posts
    5,372
    Thanks
    28
    Thanked 975 Times in 912 Posts
    Qt products
    Qt3 Qt4
    Platforms
    Unix/X11 Windows

    Default Re: Static vs. Dynamic Building for GPL Open Source Software Release

    As long as the application and all libraries are on GPL there is no problem.

  3. The following user says thank you to jacek for this useful post:

    brent99 (11th March 2008)

  4. #3
    Join Date
    Feb 2008
    Location
    Riverside, CA
    Posts
    18
    Thanks
    4
    Qt products
    Qt4
    Platforms
    Unix/X11 Windows

    Default Re: Static vs. Dynamic Building for GPL Open Source Software Release

    Just a follow-up comment for mass consumption....

    It seems to me, based on some net reading, that you can statically link GPL program to GPL library, but you should only dynamically link proprietary program to GPL library.

    Simple enough. Of course, in QT's case, that would be purchased copy of QT with proprietary program.

  5. #4
    Join Date
    Jan 2006
    Location
    Warsaw, Poland
    Posts
    5,372
    Thanks
    28
    Thanked 975 Times in 912 Posts
    Qt products
    Qt3 Qt4
    Platforms
    Unix/X11 Windows

    Default Re: Static vs. Dynamic Building for GPL Open Source Software Release

    Quote Originally Posted by brent99 View Post
    but you should only dynamically link proprietary program to GPL library.
    No, you can't link GPL libraries with proprietary applications, but it's possible with LGPL ones. It doesn't have to be dynamic linking, but it's easier to fulfill LGPL requirements with dynamic linking.

  6. #5
    Join Date
    Feb 2008
    Location
    Riverside, CA
    Posts
    18
    Thanks
    4
    Qt products
    Qt4
    Platforms
    Unix/X11 Windows

    Default Re: Static vs. Dynamic Building for GPL Open Source Software Release

    If that were true, you couldn't run proprietary apps on linux, since all the linux libraries are GPL.

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

    Default Re: Static vs. Dynamic Building for GPL Open Source Software Release

    GPL excludes libraries and tools that are "distributed as part of the system" (or something similar), so you can link closed-source apps against them.

    Besides, standard Linux libraries (such as glibc) are LGPL.

  8. #7
    Join Date
    Jan 2006
    Location
    Warsaw, Poland
    Posts
    5,372
    Thanks
    28
    Thanked 975 Times in 912 Posts
    Qt products
    Qt3 Qt4
    Platforms
    Unix/X11 Windows

    Default Re: Static vs. Dynamic Building for GPL Open Source Software Release

    Quote Originally Posted by wysota View Post
    GPL excludes libraries and tools that are "distributed as part of the system" (or something similar), so you can link closed-source apps against them.
    Yes, and I remember seeing an exception in one of the system headers that covered proprietary applications.

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.