Qt Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Unsolved

    Call for Presentations - Qt World Summit

    LGPL License and modified source code

    General and Desktop
    3
    3
    1578
    Loading More Posts
    • 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.
    • D
      der.redhead last edited by

      Good morning everybody,

      I am using Qt 4.6.2 with the LGPL license in a commercial product. For testing this product I used the QtTest module and the QSignalSpy class. The QSignalSpy enforces a Qt::DirectConnectoin which makes a stress test crash (see https://bugreports.qt-project.org/browse/QTBUG-2842 ).

      So I copied the header file qsignalspy.h and substituted Qt::DirectConnection with Qt::QueuedConnection. This solved the problem. The new header file called just signalspy.h with the class SignalSpy is only used in the unit tests for my product.

      My question is, if I have anything to do to satisfy the LGPL (because of the minor change)? Do I have to provide the modified sourcecode? And if so, to whom?

      Thanks in advance!

      Jan

      1 Reply Last reply Reply Quote 0
      • raven-worx
        raven-worx Moderators last edited by

        if you're don't publish your modifications with your product you're not violating the LGPL ... for your personal use you can modify anything you want.

        --- SUPPORT REQUESTS VIA CHAT WILL BE IGNORED ---
        If you have a question please use the forum so others can benefit from the solution in the future

        1 Reply Last reply Reply Quote 0
        • sierdzio
          sierdzio Moderators last edited by

          Both GPL and LGPL talk about distributing modified sources to users. You don't have to publish them world-wide. And since those are tests, basically you and your co-workers are those users ;)

          In this case, additionally, I think Qt-exception works and you don't need to do anything, just like raven-worx said.

          (Z(:^

          1 Reply Last reply Reply Quote 0
          • First post
            Last post