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. Open source license, source code as an option.
Forum Updated to NodeBB v4.3 + New Features

Open source license, source code as an option.

Scheduled Pinned Locked Moved Unsolved General and Desktop
6 Posts 4 Posters 440 Views 1 Watching
  • 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.
  • F Offline
    F Offline
    Feiderico.Massimi
    wrote on last edited by
    #1

    Goodmorning, I have a question about the open source license.
    By reading the license I understand that I can sell my application created with the open source license providing together with the application the source code of QT and my application.
    My doubt is, I can make the source code available as an option in my application, let me explain better, I can do something like this:

    • My basic app costs 1000 USD (without source code)

    • My application with extended functions costs 3000 USD (without source code)

    • My application with extended functions and source code costs 6000 USD

    is it possible to do such a thing respecting the opensource license?
    Thanks in advance

    jsulmJ 1 Reply Last reply
    0
    • F Feiderico.Massimi

      Goodmorning, I have a question about the open source license.
      By reading the license I understand that I can sell my application created with the open source license providing together with the application the source code of QT and my application.
      My doubt is, I can make the source code available as an option in my application, let me explain better, I can do something like this:

      • My basic app costs 1000 USD (without source code)

      • My application with extended functions costs 3000 USD (without source code)

      • My application with extended functions and source code costs 6000 USD

      is it possible to do such a thing respecting the opensource license?
      Thanks in advance

      jsulmJ Offline
      jsulmJ Offline
      jsulm
      Lifetime Qt Champion
      wrote on last edited by
      #2

      @Feiderico-Massimi Which license do you mean? If GPL then no, you can't ask for money if users ask for source code.
      If you're talking about LGPL then you do NOT have to provide your source code! You only have to provide the users the possibility to relink your app with their Qt version (usually that means to give them object files *.o).
      Note: I'm not a lawyer!

      https://forum.qt.io/topic/113070/qt-code-of-conduct

      JonBJ 1 Reply Last reply
      0
      • jsulmJ jsulm

        @Feiderico-Massimi Which license do you mean? If GPL then no, you can't ask for money if users ask for source code.
        If you're talking about LGPL then you do NOT have to provide your source code! You only have to provide the users the possibility to relink your app with their Qt version (usually that means to give them object files *.o).
        Note: I'm not a lawyer!

        JonBJ Offline
        JonBJ Offline
        JonB
        wrote on last edited by JonB
        #3

        @jsulm said in Open source license, source code as an option.:

        usually that means to give them object files *.o

        That's a new one on me! I thought if one was linking against Qt libraries as *.so/*.dll files (as publicly available, obviously not altered) users wouldn't need any re-linking, just install new version of Qt shared libs and off they go?

        SGaistS 1 Reply Last reply
        1
        • JonBJ JonB

          @jsulm said in Open source license, source code as an option.:

          usually that means to give them object files *.o

          That's a new one on me! I thought if one was linking against Qt libraries as *.so/*.dll files (as publicly available, obviously not altered) users wouldn't need any re-linking, just install new version of Qt shared libs and off they go?

          SGaistS Offline
          SGaistS Offline
          SGaist
          Lifetime Qt Champion
          wrote on last edited by
          #4

          @JonB said in Open source license, source code as an option.:

          @jsulm said in Open source license, source code as an option.:

          usually that means to give them object files *.o

          That's a new one on me! I thought if one was linking against Qt libraries as *.so/*.dll files (as publicly available, obviously not altered) users wouldn't need any re-linking, just install new version of Qt shared libs and off they go?

          That's correct. The object files are needed in case it's a static build and it's therefore way more hassle to provide than use dynamic linking.

          Interested in AI ? www.idiap.ch
          Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

          JonBJ 1 Reply Last reply
          1
          • SGaistS SGaist

            @JonB said in Open source license, source code as an option.:

            @jsulm said in Open source license, source code as an option.:

            usually that means to give them object files *.o

            That's a new one on me! I thought if one was linking against Qt libraries as *.so/*.dll files (as publicly available, obviously not altered) users wouldn't need any re-linking, just install new version of Qt shared libs and off they go?

            That's correct. The object files are needed in case it's a static build and it's therefore way more hassle to provide than use dynamic linking.

            JonBJ Offline
            JonBJ Offline
            JonB
            wrote on last edited by JonB
            #5

            @SGaist
            Sorry to ask for clarification, but...

            Static linking has not been mentioned here. Let's say I'm in the absolute normal case: I am linking against dynamic Qt libraries, I have made no changes to them, my output is an executable. I do not have to supply my own sources. Are you/ @jsulm now saying I do need to supply my own files' intermediate *.o/*.obj, perhaps so that someone else can relink if they want to use static Qt libraries or something?

            I have not heard this before. I thought I understood it all, now I am confused...

            jsulmJ 1 Reply Last reply
            0
            • JonBJ JonB

              @SGaist
              Sorry to ask for clarification, but...

              Static linking has not been mentioned here. Let's say I'm in the absolute normal case: I am linking against dynamic Qt libraries, I have made no changes to them, my output is an executable. I do not have to supply my own sources. Are you/ @jsulm now saying I do need to supply my own files' intermediate *.o/*.obj, perhaps so that someone else can relink if they want to use static Qt libraries or something?

              I have not heard this before. I thought I understood it all, now I am confused...

              jsulmJ Offline
              jsulmJ Offline
              jsulm
              Lifetime Qt Champion
              wrote on last edited by
              #6

              @JonB "The object files are needed in case it's a static build" - in case of static build.
              Since you talk about dynamic build you do not have to provide object files.

              https://forum.qt.io/topic/113070/qt-code-of-conduct

              1 Reply Last reply
              2

              • Login

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