Double clicking C++ GDExtension build errors in Build Output will jump to some files but not to others

I've been having this issue for quite some time across many different versions of Rider and figured I should report it.  I've seen some similar issues logged years ago for people developing for Unreal and Unity.

When I have build errors, double clicking the errors will lead me to *some* files and other errors only take me to the console output.  An example is in this scenario - I can click the errors linked to memory.hpp from godot-cpp and it opens them in my godot-cpp solution.  I can click the nmake.substitution.props file and it opens that file in the BFSystem solution.  If I click the BFAdvancedProductionBuilding errors, it leads me only to the console output for that build error describing the file, but will not jump to the file in the BFSystem solution.  It also does not list the BFProductionBuilding.cpp or BFProductionBuilding.h filename next to those errors like it does the other two files in that Build Output.

I did create my .sln files by hand and could have certainly done something wrong there.  I am also still using scons instead of CMake so maybe that's related, but this was an issue before CMake became the recommended build tool for Rider.

Any ideas on something I may have missed in maybe my solution or build setup?

0
1 comment

Hello Jordan, 
Thank you for contacting Rider support. I have taken a look and reproduced the issue at least partially. Indeed, there are file references in the build output that aren't clickable. Developer will take a look.

Please watch this issue for further updates: RIDER-142544 When building Godot C++ via MSBuild (.sln + .vcxproj) the errors in build output aren't clickable

Have a nice day!

1

Please sign in to leave a comment.