Important: Please read the Qt Code of Conduct -

Deploying commercial QtCreator (trial) projects as standalone programs

  • Hi all, I'm currently trying out the commercial QtCreator (trial) to build some small projects as standalone programs. In the future, I may want to deploy them for commercial purpose.

    I have successfully built projects as standalone using static opensource Qt before. However, when I built these projects (release version) using the commercial QtCreator, the program requires external dlls.

    Is there anyway to use the commercial QtCreator to build standalone programs without the need of using opensource Qt as to avoid violating the LGPL?


  • Lifetime Qt Champion


    As you already know, building a static Qt application requires that you build statically. That doesn't change. However don't forget the licensing constraint that comes with a static build.

  • @SGaist
    Thank you for your reply. I came across this article

    and had some questions. I tried to find answers to these questions but couldn't find any clear instructions so please forgive me,

    1. Does it mean that if I deploy my applications as a plugin-based built using commercial QtCreator, I can freely distribute the dlls required without any constraints?
    2. If my applications does not requires, QtHelp, QtNetwork or QtWebKit, I can deploy my application as a standalone without needing to worry about violating LGPL? If yes, is there a list of 3rd-party libraries that might have different licensing that I can use as reference?

    Thank you for your patience.


  • Lifetime Qt Champion

    1. The Qt Creator version you use doesn't matter. It's the license you have for Qt that will tell what you can and must do with your application.

    2. Here you can find a nice GPL/LGPL guide. The modules you don't need for your application, you simply don't ship.

    Note: I am not a lawyer

  • @SGaist
    Thank you for your advice. I will definitely take note of it.


Log in to reply