Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. OpenGL problems when deploying my final application
Forum Updated to NodeBB v4.3 + New Features

OpenGL problems when deploying my final application

Scheduled Pinned Locked Moved Unsolved Installation and Deployment
2 Posts 2 Posters 298 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.
  • A Offline
    A Offline
    Alexuds79
    wrote on 13 Mar 2023, 12:18 last edited by
    #1

    Hi. I have built my final application using Qt 6.4.2, compiled with cmake (CMakeLists.txt) and using the different final executable generation tools in each case (windeployqt, macdeployqt).

    My problem is that the app runs correctly in environments such as Windows 11 or MacOS 13, but not in previous versions, which either show a black window, or directly a message that warns me that "OpenGL is not installed" (as happens in Windows Server environments). I have found that by disabling the use of OpenGL, the problem disappears, as stated in the following link:

    https://doc.qt.io/QtQuick2DRenderer/

    However, by doing that, the final application loses a lot of graphics performance and shows artifacts as you move through the interface.

    Is there any way to link the OpenGL or Mesa3D libraries (preferably precompiled) so that the final executable uses these linked libraries instead of looking for those of the operating system?

    Thanks in advance :)

    J 1 Reply Last reply 13 Mar 2023, 14:15
    0
    • A Alexuds79
      13 Mar 2023, 12:18

      Hi. I have built my final application using Qt 6.4.2, compiled with cmake (CMakeLists.txt) and using the different final executable generation tools in each case (windeployqt, macdeployqt).

      My problem is that the app runs correctly in environments such as Windows 11 or MacOS 13, but not in previous versions, which either show a black window, or directly a message that warns me that "OpenGL is not installed" (as happens in Windows Server environments). I have found that by disabling the use of OpenGL, the problem disappears, as stated in the following link:

      https://doc.qt.io/QtQuick2DRenderer/

      However, by doing that, the final application loses a lot of graphics performance and shows artifacts as you move through the interface.

      Is there any way to link the OpenGL or Mesa3D libraries (preferably precompiled) so that the final executable uses these linked libraries instead of looking for those of the operating system?

      Thanks in advance :)

      J Offline
      J Offline
      JoeCFD
      wrote on 13 Mar 2023, 14:15 last edited by
      #2

      @Alexuds79 Pack OpenGL or Mesa3D libraries in your app. Also pay attention to its dependencies. Can be messy.

      On Windows, you may take a look at this
      https://learn.microsoft.com/en-us/windows/win32/dlls/dynamic-link-library-search-order

      MacOS is similar to Linux and I guess you can set running time path to OpenGL libs. Then your app will run with the packed OpenGL or Mesa3D libraries.

      1 Reply Last reply
      0

      1/2

      13 Mar 2023, 12:18

      • Login

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