Qt Forum

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

    Update: Forum Guidelines & Code of Conduct

    Solved Qt for Python - closed-source application as single executable?

    Qt for Python
    2
    5
    513
    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.
    • A
      ALIENQuake last edited by ALIENQuake

      Hello,

      I want to create application using Open Source version of Qt + Qt for Python. The distribution requirements is: it has to be single executable with all dll/files bundles inside. The application will be closed source.

      1. Can i do this technically?
      2. No licensing problems?
      1 Reply Last reply Reply Quote 0
      • Kent-Dorfman
        Kent-Dorfman last edited by

        Nope...when you use python you accept that the code is distributed in multiple files. If you must do single file executable then write it in C++ and hope that static linking is fully supported on your platform.

        Also, generally speaking you cannot do a statically linked closed source program if it contains open source code in it.

        A 1 Reply Last reply Reply Quote 0
        • A
          ALIENQuake @Kent-Dorfman last edited by ALIENQuake

          @kent-dorfman said in Qt for Python as single executable.:

          Also, generally speaking you cannot do a statically linked closed source program if it contains open source code in it.

          What do you mena by that? When I compile application and I link all dll, I'm not modifying the source of those dll library's. And if someone puts his ow version of the library's at the same folder where the executable is, Dynamic-Link Library Redirection will load those custom library's instead of the linked ones, at least on Windows. So the LGPL requirement is fulfill.

          Kent-Dorfman 1 Reply Last reply Reply Quote 0
          • Kent-Dorfman
            Kent-Dorfman @ALIENQuake last edited by

            @alienquake you inferred static linking where there is one executable (all dll/files inside). that would be verboten under LGPL.

            A 1 Reply Last reply Reply Quote 0
            • A
              ALIENQuake @Kent-Dorfman last edited by ALIENQuake

              @kent-dorfman said in Qt for Python - closed-source application as single executable?:

              @alienquake you inferred static linking where there is one executable (all dll/files inside). that would be verboten under LGPL.

              Static linking is not forbidden under LGPL. If the app uses statically linked LGPL library, all you have to do is provide your object files and the LGPL requirement is still satisfied. Or use Dynamic-Link Library Redirection feature. It's written inside LGPL FAQ: https://www.gnu.org/licenses/gpl-faq.en.html#LGPLStaticVsDynamic

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