error in visual studio when using visual GDB debugger - c++

I am building inkscape source code containing cpp files in visual studio. To compile I have used visual gdb(debugger).
by https://wiki.inkscape.org/wiki/Using_Visual_Studio following this link.
But I am facing 3 errors
1.command line action failed in visual gdb.
2.Build has failed.see the output window for more details.
3.MSB3073, makefile target error in makefile

Related

Visual Studio 2019 does not open window with source file and does not position to line with error

There are some compile errors in Errors List after CMake project compilation.
Visual Studio 2019 does not open window with source file and does not position to line with error through double click on them.
Also Intellisense not working correctly.
How can i solve this problem?
Clean build project and delete folder .vs of your solution.
You can check the following link to know more about how to fix intellisense issues in Visual Studio: https://weblog.west-wind.com/posts/2018/Aug/07/Fixing-Visual-Studio-Intellisense-Errors

Error when remote debugging a C++ app running on Linux machine with gdbserver

I'm trying to get the remote debugging to work on Visual Studio 2017 in Windows. I'm using the gdbserver option in Visual Studio project properties. The project is a make file project created in Visual Studio 2017. I'm getting following error in the output window.
And getting following error in Linux Console output window
What could be the reason for these errors?

How to run Code Analysis on x64 Project in Visual C++?

I am trying to run the code analysis of Visual Studio 2015 on my x64 VC++ project. However I get the following error:
Error C1250 Unable to load plug-in 'C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\localespc.dll'
I am activating the x64 toolset of Visual Studio by running the batch script "vcvarsall.bat amd64" before I start the IDE. Visual Studio is run with the "/useenv" option afterwards.
When I check the VC++ environment variables, I can see that the following path is contained in the PATH variable:
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\amd64
How can I tell Visual Studio to use the code analyzer (localespc.dll) from there and not the x86 version which it apparently tries to use (according to the error message).
Thanks a lot for your help!
I was having the same issue with my 64-bit C++ projects. I discovered simply renaming/removing localespc.dll from VC\bin allowed the Code Analysis builds to succeed and still report analysis warnings. It seems if VS doesn't find this dll in the VC\bin directory then it won't add the compiler switch for /analyze:plugin but otherwise passes all the other switches required by the Code Analysis.
Set the following property in your project file: <PreferredToolArchitecture>x64</PreferredToolArchitecture>
This tells Visual Studio to use the 64-bit version of various tools, including code analysis. I found How to make Visual Studio use the native amd64 toolchain helpful on the topic.
Note that renaming localespc.dll no longer solves the problem with Visual Studio 2017. It seems that setting PreferredToolArchitecture is Microsoft's intended way to do this.

C++ : Installing cvBlobLib library for Visual Studio 2015

I've been looking all over the web for a proper code for that library but whenever i try to build it using CMake 3.4.2 it gives me errors and when i try to build the resulting visual studio project (using Visual Studio 2015) it gives me errors as well and doesn't build successfully.
Is there any way to properly install this library and use it in Visual Studio 2015?
Thanks!
EDIT:
Screen shot of the error i get when pressing on "Generate":

Error building libarchive for c++ Visual Studio 2010 Professional

I am trying to build libarchive for c++ Visual Studio 2010 Professional. Everything seems to be fine, the tests run OK, up until I get the following error:
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(151,5): error MSB6006: "cmd.exe" exited with code -1073741571.
Build FAILED.
I have googled and searched for this exact error on SO but cannot find anything.
Thank you.