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. I made custom Qt minimalistic x64 MinGW-w64 build for Windows
Forum Update on Monday, May 27th 2025

I made custom Qt minimalistic x64 MinGW-w64 build for Windows

Scheduled Pinned Locked Moved Unsolved General and Desktop
4 Posts 2 Posters 734 Views
  • 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.
  • S Offline
    S Offline
    skunkoss
    wrote on last edited by
    #1

    You may wanna check it out. :) Any constructive opinions welcomed.

    https://github.com/martinrotter/mingw-w64-qt5-builds

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

      Hi and welcome to devnet,

      Thanks for the repo.

      Two things you have to watch out for:

      • Static linking -> there are licensing constraints that you have to abide to when doing a static build. See the LGPL for more details. I'd recommend rather giving instructions on how to do the static build rather than providing one like that especially since you seem to have OpenSSL and D-Bus linked.
      • OpenSSL -> there are pitfalls depending on the countries regarding cryptographically enabled applications/libraries, hence Qt dlopen's OpenSSL so every developer can use it doing the proper choice on the matter.

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

      S 1 Reply Last reply
      1
      • SGaistS SGaist

        Hi and welcome to devnet,

        Thanks for the repo.

        Two things you have to watch out for:

        • Static linking -> there are licensing constraints that you have to abide to when doing a static build. See the LGPL for more details. I'd recommend rather giving instructions on how to do the static build rather than providing one like that especially since you seem to have OpenSSL and D-Bus linked.
        • OpenSSL -> there are pitfalls depending on the countries regarding cryptographically enabled applications/libraries, hence Qt dlopen's OpenSSL so every developer can use it doing the proper choice on the matter.
        S Offline
        S Offline
        skunkoss
        wrote on last edited by
        #3

        @SGaist Added MSVC/LTCG-enabled builds too.

        https://github.com/martinrotter/qt5-minimalistic-builds

        I think AFAIK, that static linking-related discussion and LGPL controversies only matter when compilling close-source application.

        This was discussed in several places and if you allow users to have build reproducible (repo contains build scripts), then you do not violate with LGPL.

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

          That's one of the main use of the LGPL version of Qt: closed source applications. So it does matter a lot.

          As I wrote before, users of closed source LGPL applications need to be able to use a different version of Qt so the developer has to provide the means to do it and it's not just about reproducing the Qt build that was used. You have to provide all the object files for your application.

          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