Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Language Bindings
  4. Requirements to use LGPL PySide in proprietary software development
Forum Updated to NodeBB v4.3 + New Features

Requirements to use LGPL PySide in proprietary software development

Scheduled Pinned Locked Moved Language Bindings
licensingpyside
2 Posts 2 Posters 1.7k Views 2 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.
  • K Offline
    K Offline
    Kaje
    wrote on last edited by
    #1

    I'm developing a python UI proprietary software using PySide (LGPLed) library. I want to freeze my code using PyInstaller into executable format and distribute to my customers. In this situation, what are the requirements I need to follow to obey legal requirements of LGPL PySide?
    Here I don't modify anything in PySide or Qt. So do I have to distribute the source code of Qt/PySide? If not, what should I do ?
    How do I add copyright notice of PySide into my distribution?
    Please give me a link if there's any listed requirements for this purpose.

    Thank you.

    1 Reply Last reply
    0
    • SGaistS Offline
      SGaistS Offline
      SGaist
      Lifetime Qt Champion
      wrote on last edited by
      #2

      Hi and welcome to devnet,

      For licensing related question, you should contact The Qt Company directly. You should find the licensing texts directly in the sources

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

      1 Reply Last reply
      0

      • Login

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