Importing problem(urgent)

[zho8789]

Hi, I have a small Linux project which has a OpenCV as it’s dependency.

In Linux(Ubuntu: running in VMware), I’ve already compiled and built it by using bash script without any error.

In order to develop it more efficiently, I’m  going to import it into Visual Studio 2015 from Ubuntu by using VisualGDB.

According to https://visualgdb.com/tutorials/linux/import/ , I’ve imported it into VS2015 successfully, but whenever I built it, I have got a following error:

“Error MSB3073      The command “”C:\Program Files (x86)\Sysprogs\VisualGDB\\VisualGDB.exe” /build “D:\tmp\LinuxProject3\LinuxProject3\LinuxProject3.vcxproj” “/solution:D:\tmp\LinuxProject3\LinuxProject3.sln” “/config:Debug” “/platform:VisualGDB”” exited with code 1.”
In order to check out whether my project had a problem or not, I imported the source of Midnight Commander just illustrated in above link with all default setting without any changes ,  but unfortunately the result was same.

By the way, there is no error in creating(not importing) new linux C++ project ,connecting with VMware , compiling, building and  debugging in VS2015.

What’s wrong? What mistakes did I take?  Anyone has full experiences, please help me ASAP…     Thanks.

Attachments:

You must be logged in to view attached files.

[support]

Hi,

Looks like the underlying build process produced some errors that are not recognized by Visual Studio. Please use the View->Output window to see the entire build output and check it for error messages explaining what is going on.

[zho8789]

<h3>Problem solved!</h3>
The bug was in Visual GDB version 5.3!

Using v5.1 not v5.3, no building error.

Thanks for kind reply.

 

[support]

Hi,

This could have been caused by the updated toolchain engine that does automatically finds the toolchain during build instead of hardcoding its location in the project properties. Some manual modifications to the project files that previously worked with v5.1 and v5.2 would not work with v5.3 due to this update.

Either way, feel free to let us know more the details of the error you get and we can help you get v5.3 to work.

[Author]

Posts