I’m using VisualGDB 5.5r4 with an advanced CMake project.
To organize the application and libraries a little better in the solution a tried the virtual folder option.
However i noticed that the folder information is saved with absolute path in the .vgdbcmake file.
I did some experimenting with project variables but was not able to adjust it to relative paths.
So is there a way to get the virtual folders working with relative paths saved in the .vgdbcmake file?
VisualGDB should normally already use the relative paths as reported by CMake. However, if your codebase spans across multiple drive letters or some CMake files use absolute paths to refer to the source files, the absolute paths may indeed end up in the VisualGDB’s settings files.
If you can reproduce the problem on a clean project and share the steps we could follow on our side to get the same behavior, we will gladly look into it and try to suggest a workaround.