Forum Replies Created
-
Posts
-
Please try deleting the %LOCALAPPDATA%\VisualGDB\ArduinoSettings.xml file to reset all Arduino-related settings.
If this doesn’t help, please also delete the %LOCALAPPDATA%\Arduino15 folder and let VisualGDB re-download the necessary packages.
Looks like the Linux machine you are using for building is not compatible with the Raspberry Pi toolchain. Please ensure you use a 64-bit Linux machine for building the Raspberry Pi kernel.
Hi,
Good to know the sysroot sync works.
The library-related options used by GCC can be indeed very misleading, so please feel free to look through this page for an overview and examples. Also feel free to share the error messages you get and the settings you have and we can point you to the right direction.
Thanks, looks like we indeed shipped the 64-bit version of the Arduino builder instead of the 32-bit one. We have fixed it in this build: VisualGDB-5.4.103.2813.msi
OK, we have released the updated BSP. You can update it conveniently via the VisualGDB Package Manager.
Hi,
Sorry, this limitation comes from the way Clang engine handles the rename data internally. We might be able to support renaming entities from their references in one of the next major VisualGDB releases, however we won’t be able to promise a specific deadline for this as it would require a non-trivial change on our side.
Good to know you got the regular SysprogsSync to work. This is the recommended way as it’s much faster than generating temporary scripts using command-line tools.
Either way, we have added another check for the “xargs -0” option, so if it’s not supported, VisualGDB will fall back to the regular xargs syntax.
Please feel free to try this build: VisualGDB-5.4.103.2811.msi
No worries. We usually schedule the BSP updates based on the popularity of the device families. Nordic devices are quite popular (and are, in our opinion, the best choice for Bluetooth LE), so our normal internal guideline is to have a BSP ready in 1-2 months after the official SDK release. However, unfortunately we did get a few interruptions along that path, so it took longer than we expected. It should be out fully tested and supported in 1-2 weeks based on what we see currently. Sorry for the wait.
Hi,
VisualGDB itself does not provide any global shortcuts, instead it registers commands with Visual Studio so that you can set shortcuts via the Visual Studio’s options dialog.
The Find Symbols in Solution command is available in the Edit menu, so you can set a shortcut for it. Method enumeration doesn’t have a global command yet, so will try to add it in one of the next builds.
Thanks for sharing this. Yes, our internal BSP build is somewhat usable, although a few example projects from Nordic use library settings that were not present in the previous SDKs, so we are making sure that VisualGDB can clone them properly. We also understand that it took us longer than usual to process this, so we will give a higher priority to supporting the next Nordic SDK so it won’t take that long.
Hi,
The Preview Changes dialog is actually rendered by Visual Studio based on the data VisualGDB reports to it, so the amount of tweaking we could do to it is limited.
That said, reference highlighting was indeed broken in the latest VisualGDB 5.4R2, so we have fixed it in this build: VisualGDB-5.4.103.2810.msi
Hi,
Yes, we are currently running internal tests on it and expect to release it in a few next weeks (there have been non-trivial changes to the Nordic samples).
No problem and good to know it works. FYI: we are updating our installer to support VS2019, so we will try to improve the detection of multiple VS2017 installations as well.
