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. Cant build app as Debug. "No rule to make target"

Cant build app as Debug. "No rule to make target"

Scheduled Pinned Locked Moved Solved Installation and Deployment
5 Posts 3 Posters 541 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.
  • B Offline
    B Offline
    BD9a
    wrote on last edited by
    #1

    Hey, Im trying to build app as Debug, cuz I want to use Profiler (windows, external profiler). Building as Release work's fine.

    :-1: error: No rule to make target 'C:/Qt/32_5125_Static/32_5125_Static/lib/libQt5QuickControls2d.a', needed by 'debug/Minecraft-Clicker.exe'.  Stop.
    

    Im using 5.12.5 Mingw 32bit kit Static.

    Seems It's adding "-d" suffix to lib name - why?
    There is no file libQt5QuickControls2d.a but libQt5QuickControls2.a exist.

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

      Hi
      The little d is normal and means its looking for a debug version of the lib.
      Since its a static build, it might not be included.

      B 1 Reply Last reply
      0
      • mrjjM mrjj

        Hi
        The little d is normal and means its looking for a debug version of the lib.
        Since its a static build, it might not be included.

        B Offline
        B Offline
        BD9a
        wrote on last edited by BD9a
        #3

        @mrjj Fug, it's possible to add those files / modify statc build?

        mrjjM 1 Reply Last reply
        0
        • B BD9a

          @mrjj Fug, it's possible to add those files / modify statc build?

          mrjjM Offline
          mrjjM Offline
          mrjj
          Lifetime Qt Champion
          wrote on last edited by
          #4

          @BD9a
          Only by recompiling it as debug version as far as i know.
          You could just use a non static Qt and debug in that if you just want to
          Profile some of your own code ?

          1 Reply Last reply
          0
          • KH-219DesignK Offline
            KH-219DesignK Offline
            KH-219Design
            wrote on last edited by
            #5

            There is a flag to tell qmake that you want debug symbols no matter what the optimization level of the build is.

            qmake CONFIG+=force_debug_info "$DIR"
            

            Full running example: https://github.com/219-design/qt-qml-project-template-with-ci/pull/37/files

            Especially since you mention profiling, that might serve your use case BETTER than a debug build. Debug build is going to have bottlenecks that an optimized build won't have, so you may end up focused on fixing bottlenecks that wouldn't have been there in the Release build anyway. (I assume that @BD9a already knows that. I am just stating it for the general public who may come and read this thread later.)

            www.219design.com
            Software | Electrical | Mechanical | Product Design

            1 Reply Last reply
            1

            • Login

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