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. Licensing for discontinued Qt Solutions projects
QtWS25 Last Chance

Licensing for discontinued Qt Solutions projects

Scheduled Pinned Locked Moved General and Desktop
8 Posts 6 Posters 6.0k Views
  • 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.
  • C Offline
    C Offline
    changbiyuan
    wrote on 22 Feb 2011, 01:33 last edited by
    #1

    Hi, I'd like to use QtToolBarDialog in my project. I notice Qt Solutions are no more, though the source for some of them has been put in the qt.gitorious.org repository. The .h and .cpp files for the projects in that repository have been modified to reflect the more flexible BSD licensing. However, QtToolBarDialog is not one of the projects that was moved there.

    I see that the blog post announcing the discontinuing of Qt Solutions (http://blog.qt.nokia.com/2010/11/09/qt-4-7-1-and-qt-mobility-1-1-0-released/) says, "The remaining components will be removed from Qt’s product portfolio." So what does this mean, licensing-wise, if I want to use that code? The source files from older releases will still contain the Commercial/LGPL/GPL boilerplate. If I make source modifications, how will I fulfill the LGPL requirement to share those changes, if the project is no longer in Qt's "portfolio"?

    I notice in the case of QtToolBarDialog specifically that an incarnation of it exists in the main source (under tools/shared). However, it contains a warning saying "This file is not part of the Qt API. It exists for the convenience of Qt Designer. This header file may change from version to version without notice, or even be removed. We mean it." So referencing it directly doesn't seem wise from a perspective of code maintainability. Again though the most suitable license (for me) in the files is LGPL; is there any way I can copy and paste the majority of the code in these files into my own project, and somehow make it legit?

    Thanks for any thoughts.

    1 Reply Last reply
    0
    • A Offline
      A Offline
      AndyS
      Moderators
      wrote on 22 Feb 2011, 16:22 last edited by
      #2

      This is a rather interesting situation actually, I believe I have a means of how this can be resolved while still being able to comply with the LGPL license terms in your application. Before I can give details on this I need to get this checked with our legal team so I will do that and get back to you as soon as I can with a definitive answer.

      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      1 Reply Last reply
      0
      • A Offline
        A Offline
        AndyS
        Moderators
        wrote on 23 Feb 2011, 07:28 last edited by
        #3

        I have now received confirmation from the legal team about this so the following approach should hopefully give you what you are after.

        • Copy the code for QtToolBarDialog and make a library based project using it.
        • Modify the code so that it can be built as a library (this would include exporting the symbols so that they can be found at link time)
        • Now your application can dynamically link against this library and subsequently means your application can create instances of QtToolBarDialog

        In order to comply with the LGPL now you need to distribute the original QtToolBarDialog code and a separate patch with your modifications to it so that it could be built as a library. This enables users to create their own compatible version of the library using QtToolBarDialog and to drop in a replacement of it to use in your application as per the terms of the LGPL.

        If you need further clarification on this then please let me know :)

        Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

        1 Reply Last reply
        0
        • T Offline
          T Offline
          troubalex
          wrote on 23 Feb 2011, 09:47 last edited by
          #4

          Thanks, Andy! :)

          THE CAKE IS A LIE
          Web Community Manager - Qt Development Frameworks

          1 Reply Last reply
          0
          • A Offline
            A Offline
            andre
            wrote on 23 Feb 2011, 10:12 last edited by
            #5

            [quote author="AndyS" date="1298446112"]I have now received confirmation from the legal team about this so the following approach should hopefully give you what you are after.

            • Copy the code for QtToolBarDialog and make a library based project using it.
            • Modify the code so that it can be built as a library (this would include exporting the symbols so that they can be found at link time)
            • Now your application can dynamically link against this library and subsequently means your application can create instances of QtToolBarDialog

            In order to comply with the LGPL now you need to distribute the original QtToolBarDialog code and a separate patch with your modifications to it so that it could be built as a library. This enables users to create their own compatible version of the library using QtToolBarDialog and to drop in a replacement of it to use in your application as per the terms of the LGPL.

            If you need further clarification on this then please let me know :) [/quote]
            IANAL, but...
            Sounds like this would certainly satisfy the LGPL requirements, but it also sounds like you're asking too much. Why would you require that the sources be distributed in the form of the original code + a patch? Isn't providing the modified code itself enough to satisfy the LGPL requirements? I would agree that doing it this way would be convenient for people who would like to use a later build of QtToolBarDialog than the one used to build the library, but I doubt the LGPL requires you do provide this convenience.

            1 Reply Last reply
            0
            • G Offline
              G Offline
              goetz
              wrote on 23 Feb 2011, 12:16 last edited by
              #6

              Hi Andy,

              so QtToolBarDialog in its unmodified form actually is licensed under LGPL? I think this was the question in the first place, since it is not officially available from Trolltech/Nokia anymore.

              http://www.catb.org/~esr/faqs/smart-questions.html

              1 Reply Last reply
              0
              • S Offline
                S Offline
                Smar
                wrote on 23 Feb 2011, 13:25 last edited by
                #7

                Qt solutions (old Qt Labs stuff?) are licenced under LGPL, but if you change them, you need to provide the source code. If you don’t, providing the source code should fall to Nokia, though it’d be nice to do it yourself in such case.

                Also remember than some of those solutions are not exactly “high quality code” which makes modifying them to do their job better is often needed, effectively making the modifier forced to provide the code.

                Offtopic, but... I’d still like those old Jambi pieces :)

                1 Reply Last reply
                0
                • C Offline
                  C Offline
                  changbiyuan
                  wrote on 23 Feb 2011, 18:44 last edited by
                  #8

                  Thanks Andy and everyone for your replies and comments!

                  We have another LGPL component in our software that we've had to package in such a way.

                  In this case since I would probably make quite extensive modifications to the QtToolBarDialog, I may just write equivalent functionality from scratch to avoid the hassle. Ironic that the other former Qt Solutions, which are being maintained presumably because they're of higher quality, could be put to use much more easily than the abandoned ones!

                  1 Reply Last reply
                  0

                  1/8

                  22 Feb 2011, 01:33

                  • Login

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