How to change the path of the executable for debugging in qt creator
-
I am using qt creator 2.6.0 for a while with MinGW 4.6.2 (32 bit). In the .pro file I am setting the DEST_DIR to a special folder where all executable reside. I have added recently MingW (dual target 32/64 bit) as a second tool chain. Now the DEST_DIR is set to a different dir to distinguish between the different executable versions.
The DEST_DIR is set correctly in the .pro file. That is checked by printing the content. The executable is linked and placed where it should be.
However, only the executable for the first tool-chain can be used in the debugger. The path is showing to the correct executable. When switching to the second tool-chain and checking in run the path of the first tool-chain is shown.How can I get access to the proper executable?
-
Use proper shadow building in favor of hacking around in qmake... I know, that is not a real solution.
How do you switch toolchains? Are you going into the kit and change them there or are you switching kits?
-
[quote author="Tobias Hunger" date="1360156308"]Use proper shadow building in favor of hacking around in qmake... I know, that is not a real solution.[/quote]
I would prefer to use shadow builds. My only critics are the location. If there would be the possibility to refer to one location and not directly aside of the source folder, I would be completely happy.
The reason is that I have a central "Source" folder and I am backing up this including all sub-folders regularly.
BTW. I am using the shadow-build now. However, it is used to store the tool-chain specific makefiles.[quote author="Tobias Hunger" date="1360156308"]
How do you switch toolchains? Are you going into the kit and change them there or are you switching kits?[/quote]
I am switching tool-chains under "Projects" >> "Build&Run". Alternatively, I used the functionality on the left where you can switch only the current project. I could not detect a different behaviour.
The "funny" thing is that any adjustments of the DESTDIR naming are taken over directly. Only the distinction between both tool-chains are providing the problem.
Even removing the 32 bit tool-chain for the project did not solve the problem.
Also changing the default tool-chain was not switchable. I am changing to the other installation now for a check.[edits in the first part post, koahnig]
-
So you click on another kit in the projects mode to switch tool chains? There should not be a tool chain for selection anywhere in Projects mode in Creator 2.6...
Our qmake parser is intentionally less correct than the qmake one as we want the "overall" configuration of the project, not the specific one for this one build-configuration of it. Maybe that is biting you, but I know two little about the qmake parser to be sure.
-
[quote author="Tobias Hunger" date="1360165740"]So you click on another kit in the projects mode to switch tool chains? There should not be a tool chain for selection anywhere in Projects mode in Creator 2.6...
[/quote]
I mean this here
!http://db.tt/gHmzIpNW(Project->Build&Run Menu)!
When you click on either box it is changing the tool-chain. All the content of the dialog boxes are adjusted and also the project stuff on the left bar is changed accordingly.