[support]

Hi,

Sorry for the confusion. If you want to be able to easily migrate between the toolchains and BSP versions, please don’t convert your projects to stand-alone ones. The regular VisualGDB projects don’t hardcode any toolchain-specific (or BSP-specific) flags, so you can easily switch BSPs, toolchains, FP modes and other settings for them. The stand-alone projects are specifically designed for the case where you don’t want to rely on VisualGDB to manage your settings and want to be able to tweak them manually.

If you used the stand-alone projects due to a different reason, please feel free to share your constraints and we will try to suggest a better way of satisfying them without losing the convenience of the regular non-stand-alone projects.

[support]

Hi,

Thanks for confirming this. Then it looks like the project file itself is missing some of the elements the normal .vcxproj files should have. The easiest way to pinpoint this would be to use a diffing tool (e.g. KDiff3) to compare the 2 .vcxproj files side-by-side and try editing one of them to make it as close as possible to the other one. Once you encounter the step that causes this problem, you should be able to revert it on the other project to fix it.

[support]

Hi,

Strange. Could you please try creating a new MSBuild-based VisualGDB Linux project from scratch and confirm that the problem still persists? If yes, what are the contents of the C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VC\VCTargets\Platforms\VisualGDB folder?

[support]

Hi,

Thanks for the linker command line. It looks like a project created with an older version of the toolchain that didn’t support disabling semihosting yet. In order to be able to fully remove semihosting code from the project, please re-create it with our latest ARM toolchain based on GCC 7.2.0.

[support]

Hi,

This looks like CMake doesn’t report some of the target information to VisualGDB. This is to be expected, as unit tests projects are not officially supported for Advanced CMake yet. That said, we might be able to investigate/fix this if you could create a basic repro project and send it to us (or attach it here).

[support]

Hi,

Thanks for the update. Normally the VisualGDB platform should be installed to the following path:

C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VC\VCTargets\Platforms\VisualGDB

Please double-check that this directory exists. If it doesn’t, please double-check that the VS installation path in registry is correct:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\SxS\VS7\15.0

Below is an example of a correct value:

C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\

If you change the VS path in the registry, please uninstall and reinstall VisualGDB so that it can pick up the updated path.

[support]

Hi,

Strange. Another option would be to uninstall VisualGDB, repair the VS installation via the VS Installer, and install VisualGDB back. If this still doesn’t help, please let us know which Visual Studio version you are using and where is it installed and we will provide more detailed steps on diagnosing MSBuild-related files.

[support]

Hi,

Looks like there is some sort of a configuration problem. If you are using the Advanced CMake Project Subsystem, it should not create any .props files and the project file extension should be .vgdbcmake, not .vcxproj. If you are not sure, please attach the screenshots of Solution Explorer and the first page of the wizard when you create a project and we will help you understand what is going on.

[support]

Hi,

Looks like you have accidentally deleted the VisualGDB MSBuild platform. Please try repairing VisualGDB via Control Panel -> Add/Remove Programs.

[support]

Hi,

If you are using CMake, please try the new Advanced CMake Project Subsystem. It is designed to query the compiler configuration directly from CMake and should produce much more accurate results.

[support]

Hi,

Thanks for renewing your support. We have investigated the problem and it looks like the VisualKernel 3.0 Beta is interfering with the VisualGDB test discovery functionality. We have located and fixed the problem. Please try this VisualKernel build, it should no longer cause conflicts with VisualGDB: http://sysprogs.com/files/tmp/VisualKernel-3.0.1.2143.msi

[support]

Hi,

Please try removing the entire contents of the file and see if his helps the compilation. If it does, put half of the contents back and check again. Repeating this a few times, narrowing the scope each time should help pinpoint the location of the character.

Another option would be to try saving the file under  a different encoding via File -> Save As (GCC may not support rare encodings that VS might be aware of).

[support]

Hi,

Good to know it works. VisualGDB actually warns about this when you create a project. If you are not familiar with the GNU tools internals, please do follow the VisualGDB suggestions – they are designed to save your time.

[support]

Hi,

Thanks for the explanation. Please try using the team settings as shown in this tutorial: https://visualgdb.com/tutorials/ci/tfs/

Please configure your CI server to set the AGENT_WORKFOLDER environment variable to any non-empty value so VisualGDB will detect that it’s running from a build server and will apply team settings & rebuild the missing files fully automatically.

[support]

Hi,

Please don’t use paths with spaces for your projects, as this confuses many GNU tools. Simply moving the project to a different path and reopening it should fully solve this.

[Author]

Posts