Relative paths in NSight Profiler
(Crossposted from the CUDA forum, in case anyone in here has more insight!) Hi, I'm trying to set up some NSight Profiler .nvact files for the whole team to use, so that they can just launch a preconfigured profile instead of setting it all up themselves every time. However, I have run into a bit of a problem; all of the paths are fixed and fully resolved, and there does not seem to be any useful way to expand variables/macros. So for example, my .nvact file has the path to the application stored as D:\Project\bin\app.exe But my teammate has his dev system set up differently, and his application is at D:\Projects\Project\bin\app.exe Obviously the profiler will not find the binary, and will be unable to launch. I really want to be able to use the Visual Studio built in variables, so that I could have $(SolutionDir)\..\bin\app.exe instead. This would be usable for all members of the team, regardless of where their code is checked out. Is there some mechanism for expanding variables that I am missing? Or is this just not possible in the current version of NSight?
(Crossposted from the CUDA forum, in case anyone in here has more insight!)

Hi,

I'm trying to set up some NSight Profiler .nvact files for the whole team to use, so that they can just launch a preconfigured profile instead of setting it all up themselves every time. However, I have run into a bit of a problem; all of the paths are fixed and fully resolved, and there does not seem to be any useful way to expand variables/macros.

So for example, my .nvact file has the path to the application stored as

D:\Project\bin\app.exe

But my teammate has his dev system set up differently, and his application is at

D:\Projects\Project\bin\app.exe

Obviously the profiler will not find the binary, and will be unable to launch.

I really want to be able to use the Visual Studio built in variables, so that I could have

$(SolutionDir)\..\bin\app.exe

instead. This would be usable for all members of the team, regardless of where their code is checked out.

Is there some mechanism for expanding variables that I am missing? Or is this just not possible in the current version of NSight?

#1
Posted 02/03/2017 03:16 PM   
Hello James, Nsight profiler doesn't support the vs env var like $(SolutionDir), I will raise a bug for dev to track. Best Regards Harry
Hello James,

Nsight profiler doesn't support the vs env var like $(SolutionDir), I will raise a bug for dev to track.

Best Regards
Harry

#2
Posted 02/06/2017 02:46 AM   
[quote=""]Hello James, Nsight profiler doesn't support the vs env var like $(SolutionDir), I will raise a bug for dev to track. Best Regards Harry[/quote] Hi Harry, Has this issue been resolved in NSight 5.4? I see the following in the release notes: "An issue with projects not recognizing the working directory in NVIDIA Nsight's or Visual Studio's project properties has been fixed. (56837) " Which sounds like it could be referring to this problem. But I still cannot resolve Visual Studio variables in NSight.
said:Hello James,

Nsight profiler doesn't support the vs env var like $(SolutionDir), I will raise a bug for dev to track.

Best Regards
Harry


Hi Harry,

Has this issue been resolved in NSight 5.4? I see the following in the release notes:

"An issue with projects not recognizing the working directory in NVIDIA Nsight's or Visual Studio's project properties has been fixed. (56837) "

Which sounds like it could be referring to this problem. But I still cannot resolve Visual Studio variables in NSight.

#3
Posted 11/07/2017 11:16 AM   
This bug appears to still be unresolved in 5.5.
This bug appears to still be unresolved in 5.5.

#4
Posted 01/08/2018 11:35 AM   
Scroll To Top

Add Reply