How can I achieve the effect of 'creator-preferences-debugger-source code mapping' in CMake scripts
-
@warning I suspect you are going to have to explain what this question means.
Is "creator-preferences-debugger-source code mapping" this?
That's "Source path mapping" not "source code mapping".How does that relate in any way to CMake scripts (by which I assume you mean CMakeLists.txt)? The debugger has no part to play in source code editing or the build configuration phase.
Why do you think that system environment variables have any part to play here? -
@warning I suspect you are going to have to explain what this question means.
Is "creator-preferences-debugger-source code mapping" this?
That's "Source path mapping" not "source code mapping".How does that relate in any way to CMake scripts (by which I assume you mean CMakeLists.txt)? The debugger has no part to play in source code editing or the build configuration phase.
Why do you think that system environment variables have any part to play here?@ChrisW67
You're right, it's "source path mapping" not "source code mapping", my mistake.I looked at the source code of QtCreator (briefly), I looked at the "signal-slots" corresponding to "source path mapping" but I didn't see where the value saved by "source path mapping" is finally used.
So I guess there might be a system environment variable (maybe not a system environment variable, but some command line parameter passed to the debugger) that is related to "source path mapping", so that when the user modifies the "source path mapping" in the creator, the debugger can get the value of the user's modification.
Based on this guess, if there is indeed an environment variable that is related to this, then I can change this environment variable in CMakeLists.txt.