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. Problem with plugins trying to debug
Forum Updated to NodeBB v4.3 + New Features

Problem with plugins trying to debug

Scheduled Pinned Locked Moved Unsolved General and Desktop
5 Posts 2 Posters 1.1k 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.
  • J Offline
    J Offline
    JonexElectronic
    wrote on last edited by JonexElectronic
    #1

    Hi.
    I am having the following problem: I am trying to debug a Qt app, but I need to do it in a specific directory. I manually copied my app because it did not deploy automatically when I compiled and ran it. I also ran windeployqt myapp.exe, which deployed all the necessary DLLs and plugins. When I try to run my app by double clicking it, it works perfectly, but when I try to run it using Qt Creator, I get some errors.

    QFactoryLoader::QFactoryLoader() checking directory path "F:/myapp/bin/WIN10_32-Debug/platforms" ...
    qt.qpa.plugin: Could not find the Qt platform plugin "windows" in ""
    

    In my build environment, I set QT_DEBUG_PLUGINS to 1, but no information is being given to me.
    F:/myapp/bin/WIN10_32-Debug/platforms
    It is not my working directory, it is where my bin is saved ... In my project it is D:\simus\myapp

    JonBJ 1 Reply Last reply
    0
    • J JonexElectronic

      Hi.
      I am having the following problem: I am trying to debug a Qt app, but I need to do it in a specific directory. I manually copied my app because it did not deploy automatically when I compiled and ran it. I also ran windeployqt myapp.exe, which deployed all the necessary DLLs and plugins. When I try to run my app by double clicking it, it works perfectly, but when I try to run it using Qt Creator, I get some errors.

      QFactoryLoader::QFactoryLoader() checking directory path "F:/myapp/bin/WIN10_32-Debug/platforms" ...
      qt.qpa.plugin: Could not find the Qt platform plugin "windows" in ""
      

      In my build environment, I set QT_DEBUG_PLUGINS to 1, but no information is being given to me.
      F:/myapp/bin/WIN10_32-Debug/platforms
      It is not my working directory, it is where my bin is saved ... In my project it is D:\simus\myapp

      JonBJ Online
      JonBJ Online
      JonB
      wrote on last edited by
      #2

      @JonexElectronic said in Problem with plugins trying to debug:

      In my build environment, I set QT_DEBUG_PLUGINS to 1, but no information is being given to me.

      This must be set at runtime, not at build time, to get diagnostic output from the application startup.

      J 1 Reply Last reply
      0
      • JonBJ JonB

        @JonexElectronic said in Problem with plugins trying to debug:

        In my build environment, I set QT_DEBUG_PLUGINS to 1, but no information is being given to me.

        This must be set at runtime, not at build time, to get diagnostic output from the application startup.

        J Offline
        J Offline
        JonexElectronic
        wrote on last edited by JonexElectronic
        #3

        @JonB yes, it is in run settings
        fa9a54a6-d200-4dfd-adbf-bb5e78194da3-image.png

        JonBJ 1 Reply Last reply
        0
        • J JonexElectronic

          @JonB yes, it is in run settings
          fa9a54a6-d200-4dfd-adbf-bb5e78194da3-image.png

          JonBJ Online
          JonBJ Online
          JonB
          wrote on last edited by
          #4

          @JonexElectronic
          Then you should be getting voluminous diagnostic output, just as everyone else does. Check each of the debugger's "output panes". I believe it goes there from Creator even under Windows, where it may be that diagnostic does not appear on standard output/error.

          J 1 Reply Last reply
          0
          • JonBJ JonB

            @JonexElectronic
            Then you should be getting voluminous diagnostic output, just as everyone else does. Check each of the debugger's "output panes". I believe it goes there from Creator even under Windows, where it may be that diagnostic does not appear on standard output/error.

            J Offline
            J Offline
            JonexElectronic
            wrote on last edited by JonexElectronic
            #5

            @JonB Yes, I should be getting that information. But this only happens to me when I have not run windeployqt on the app. Because if I have run windeployqt, the app does not run and no debug information is displayed.
            Any idea??

            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