User forums > Help

Virtual Targets and Debugger (and defines)

<< < (2/2)

oBFusCATed:
Can you post minimal project that can be used for testing?

White-Tiger:
Real targets:
debug = GCC
debug 2 = MSVC
Virtual targets:
vdebug = debug
vdebug 2 = debug 2

If you debug "vdebug" and select "debug" as target, it will debug using GDB and works fine.

If you debug "vdebug 2" and also select "debug 2" as target, it will still debug using GDB because GCC is the projects default compiler. Even though "debug 2" uses MSVC. If you what so ever debug "debug 2" directy, it'll use CDB correctly.

You can of course use 64bit GCC instead of MSVC for the "debug 2" target when "debug" uses 32bit GCC, doesn't matter which one.... I've simply chose GCC and MSVC because it makes the difference very clear. Also because I know you've guys got GCC... and I didn't know another compiler you've guys got.. Basically it doesn't matter... all that matters is that the 2nd target uses a different compiler which at least won't work with the same debugger as the first target / projects default compiler.

Also I didn't include a test case for different defines used by different compilers.. this would require more knowledge about your setup.. such as do you have 32bit and 64bit compilers, do you have MSVC, etc. But the defines used for a virtual target are also from the projects default compiler and not the compilers used by the actual targets. (and those defines are used for code completion / code highlighter. They always use the targets defines/compiler but not for virtual targets)

oBFusCATed:
Confirmed, the fix will require quite a lot of changes so it might take a while to fix.

Navigation

[0] Message Index

[*] Previous page