Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. qt vs tools, executable directories not work
Forum Update on Monday, May 27th 2025

qt vs tools, executable directories not work

Scheduled Pinned Locked Moved Solved Qt Creator and other tools
5 Posts 2 Posters 594 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
    jronald
    wrote on 5 Nov 2019, 10:28 last edited by jronald 11 May 2019, 10:48
    #1

    e.g. the project depends on a.dll

    set it:

    1. In project property / VC++ Directories / Executable Directories, add directory path of a.dll
    2. In project property / Debugging / Environment, add $(ExecutablePath). In the environment Evaluated value, I can see the directories are there and right.

    I'm sure the method works for my non Qt project.

    J 1 Reply Last reply 5 Nov 2019, 10:56
    0
    • J jronald
      5 Nov 2019, 10:28

      e.g. the project depends on a.dll

      set it:

      1. In project property / VC++ Directories / Executable Directories, add directory path of a.dll
      2. In project property / Debugging / Environment, add $(ExecutablePath). In the environment Evaluated value, I can see the directories are there and right.

      I'm sure the method works for my non Qt project.

      J Offline
      J Offline
      JonB
      wrote on 5 Nov 2019, 10:56 last edited by JonB 11 May 2019, 10:56
      #2

      @jronald
      Maybe the DLL(s) have further dependent DLLs which are still not on path? Use a dependency walker on them? Compare your added directories to exactly whatever VS would have, if you can do that?

      J 3 Replies Last reply 5 Nov 2019, 11:08
      0
      • J JonB
        5 Nov 2019, 10:56

        @jronald
        Maybe the DLL(s) have further dependent DLLs which are still not on path? Use a dependency walker on them? Compare your added directories to exactly whatever VS would have, if you can do that?

        J Offline
        J Offline
        jronald
        wrote on 5 Nov 2019, 11:08 last edited by jronald 11 May 2019, 14:01
        #3

        @JonB said in qt vs tools, executable directories not work:

        @jronald
        Maybe the DLL(s) have further dependent DLLs which are still not on path?

        No, if the same directory paths are added in system environment, it runs. And it's a project I'm migrating from wxWidgets, I'm sure the paths are enough.

        1 Reply Last reply
        0
        • J JonB
          5 Nov 2019, 10:56

          @jronald
          Maybe the DLL(s) have further dependent DLLs which are still not on path? Use a dependency walker on them? Compare your added directories to exactly whatever VS would have, if you can do that?

          J Offline
          J Offline
          jronald
          wrote on 5 Nov 2019, 14:26 last edited by
          #4

          @JonB

          By default, i.e. add PATH=$(ExecutablePath), it doesn't work, the result is as below:

          PATH=$(ExecutablePath)$(LocalDebuggerEnvironment)
          

          whichs is equivalant to:

          PATH=$(ExecutablePath)
          PATH=%PATH%;$(QtDllPath)
          

          The one below works, the key point is not check Inherit from parent or project defaults.

          PATH=$(ExecutablePath)$(QtDllPath)
          
          1 Reply Last reply
          0
          • J JonB
            5 Nov 2019, 10:56

            @jronald
            Maybe the DLL(s) have further dependent DLLs which are still not on path? Use a dependency walker on them? Compare your added directories to exactly whatever VS would have, if you can do that?

            J Offline
            J Offline
            jronald
            wrote on 5 Nov 2019, 14:28 last edited by jronald 11 May 2019, 14:30
            #5

            @JonB

            By default, i.e. add PATH=$(ExecutablePath), it doesn't work, the result is as below:

            PATH=$(ExecutablePath)$(LocalDebuggerEnvironment)
            

            whichs is equivalant to:

            PATH=$(ExecutablePath)
            PATH=%PATH%;$(QtDllPath)
            

            The one below works, the key point is not to check Inherit from parent or project defaults.

            PATH=$(ExecutablePath)$(QtDllPath)
            

            BTW, where to report the bug?

            1 Reply Last reply
            0

            1/5

            5 Nov 2019, 10:28

            • Login

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