Sysprogs forums › Forums › VisualGDB › First use of VisualGDB….
- This topic has 2 replies, 2 voices, and was last updated 2 years, 8 months ago by Mr Fox.
-
AuthorPosts
-
March 18, 2022 at 04:19 #32425Mr FoxParticipant
Hi all. I haven’t used C++ for 20 years so please bear with me. Though I had 12 years commercial C++ before that and now have 20 years commercial C# experience.
Anyway. I find I need to build a small program for RPI and I loathe Python, so I thought, how hard can it be, right? 🙂
I am using VS2022 community on a Win10 platform. RPI has latest Debian-ish Raspberry OS.
I followed the instructions at
https://visualgdb.com/tutorials/raspberry/crosscompiler/
and got everything up and running:
Linux project wizard, Application, MSBuild, Raspberry Pi cross toolchain, linked OK to the RPI via SSH
except when the project template wizard finished I got an exception:
VisualGDB version: 5.6.104.4534
------------------ System.ArgumentException ------------------
System.ArgumentException: Invalid ruleset name: ConfigurationGeneral
at g22.SetCustomPropertyValue(String a, String b, String c)
at xx.k(cw1 a, IProjectEditContext c, o b, nz1 d, t f, Boolean g, z[] e)
at uk3.i(LinuxWizardState d, cw1 a, String b, String e, nz1 c)
at uk3.DoRunWizardOrThrowException(nz1 a, String c, String b)
at r22`1.Execute(Object e, IntPtr a, Object[]& c, Object[]& b, wizardResult& d)</code>
<code>trace=[g22.SetCustomPropertyValue:41, xx.k:404, uk3.i:523, uk3.DoRunWizardOrThrowException:642, r22`1.Execute:210]And building I get
Severity Code Description Project File Line Suppression State
Error MSB4019 The imported project "C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v160\Microsoft.cpp.targets" was not found. Confirm that the expression in the Import declaration "C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v160\\Microsoft.cpp.targets" is correct, and that the file exists on disk. LinuxProject2 C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.Cpp.ToolsetLocation.targets 21
When I look at the HelloWorld example code (I have Resharper C++ installed) I see that
#include <iostream>
isn’t found.The VisualGDB blurb said it was clever and would sort out all the includes…. so I’m worried.
Conversely it’s entirely possible I’ve just not installed something right.Thoughts? Many thanks.
March 18, 2022 at 08:41 #32431supportKeymasterHi,
It looks like your VisualGDB installation is corrupt (missing MSBuild platform), or you have edited the project in a way that breaks MSBuild integration. In order to resolve it, please try:
- Uninstalling VisualGDB completely and deleting its directory
- Installing it again
- Following the tutorial to the letter to create a new project from scratch.
If it still doesn’t work, provide complete and detailed steps to reproduce the issue as described below:
- The steps should begin with launching Visual Studio. They should include every step necessary to create the project from scratch and reproduce the issue.
- Please make sure the steps do not involve any 3rd-party code as we will not be able to review it. If the problem only happens with a specific project, please make sure you can reproduce it on a clean project created from scratch.
- The steps should include uncropped screenshots of all wizard pages, VisualGDB Project Properties pages and any other GUI involved in reproducing the problem. This is critical for us to be able to reproduce the problem on our side.
You can read more about the best way to report VisualGDB issues in our problem reporting guidelines, If you do not wish to document the repro steps and save the screenshots, please consider recording a screen video instead and sending us a link to it.
Please note that many VisualGDB issues are caused by selecting an incompatible combination of settings at some point. We are generally not able to review specific projects and find the specific settings that were set incorrectly. We recommend checking the projects into source control and keeping a track of all changed settings to avoid breaking the projects.
You can also try checking various diagnostic output from various parts of VisualGDB as described on this page. Although we won’t be able to review it for a specific project unless the we can reproduce the problem from scratch, checking it might provide some clues on what is causing the unexpected behavior.
March 18, 2022 at 13:32 #32436Mr FoxParticipantSolution: Install VS2022 C++ (I just had C#) BEFORE installing VisualGDB…. 🙂
-
AuthorPosts
- You must be logged in to reply to this topic.