[Zoellick]

Hello!

I’d checked the link before asked on test project, followed all steps precisely, but had no success. Still MS-like configuration created. Also tried Android approach without success. I hadn’t found any NMake reference in $(VISUALGDB_DIR) and have no idea where to dig. Changing build system isn’t possible, at least any time soon.

Thanks for advice on path mapping, works almost as desired. Although when I use project variables like $(ProjectDir) in paths, in setting editor GUI they are substituted correctly, but in GDB Session they don’t expand what leads to a manual editing of mapping for every user. Is there a workaround for the situation?

[Zoellick]

Pls, ignore “Another thing I noticed while setting debug environment is when I use Attach to process dialog” paragraph – it’s totally my fault.

[Zoellick]

Hello!

Thank you!

Attach options – is definitely what I needed! Thanks!
Although “set debug-file-directory” added in additional GDB commands isn’t working. Possibly because of the target is set on gdb startup and debug-file-directory has no effect. Workaround is to replace this command with “file $(TargetDir)/executable.debug”. Symbols will be forced to load from given file.

What for “The virtual folder bug” is I’m using VisualGDB 5.4 Preview 7, so it doesn’t seem to be fixed.

As for IntelliSense, I’ll research it lately, as it’s less priority problem.

Another thing I noticed while setting debug environment is when I use Attach to process dialog, Visual GDB is looking for config named $(ProjectName)-$(Configuration).vgdbsettings, but not $(ProjectName)-$(Configuration)-$(Platform).vgdbsettings as set in NMake output. I see that the target platform may be different from one chosen in VS build settings, but is it reliable to assume VisualGDB will look for $(ProjectName)-$(Configuration).vgdbsettings while attaching to any remote process?

And one more question I forgot to ask.
I added VisualGDB support for all 30+ projects next way:
at first I created a template project with default settings, which was custom build project with NMake settings,
then I copied and renamed all .vgdsettings into project directories and renamed them respectively to project names
than thing gone wrong. When I added new configurations in VS Configuration Manager, it was added as MsBuild configuration, not NMake.
Workaround for me was editing each .vcxproj file manually, which doesn’t seem right to me.
Is there any way to get Nmake project, adding GDB Debug configuration to project, instead of MsBuild configured project?

Thanks to your support!

[Author]

Posts