I assume you are planning support for the Pico as native build, is this the case?
Will you be able to support remote build/debug on the raspberry pi?
I’ve had a go and making and importing using the cmake build setup RPi foundation provide for the pico, with no success.
I’m guessing its because they use a new minimum version of cmake and thus cmake features that perhaps you don’t support?
There is no advantage on building the code for Raspberry Pi Pico on a regular Raspberry Pi and it is not practical to build the code on the Pico itself. Hence VisualGDB will build the code directly on Windows using a cross-toolchain. You will be able to use a regular Raspberry Pi as a debug probe if you prefer this option.
You can try this build: VisualGDB-184.108.40.20633.msi. It has partial for the Pico SDK (allowing to clone and build projects), but debugging still needs to be configured manually (you can use this OpenOCD executable with the official Raspberry Pi scripts) and the GUI for editing the PicoSDK configuration variables won’t apply them yet. The official release with the missing functionality added is expected next week.
No worries. We ask users to confirm/renew support for issues that require investigation on our side. Raspberry Pi Pico is getting a lot of attention recently, and we are working on supporting it anyway, so we are happy to share the latest preview build with anyone interested in trying it out.
This is a win for VisualGDB, as from what I’ve read, it’s currently a pain to setup the Pico for proper C/C++ development. I’m also looking to evaluate the Pico at some point and as expected, variants have already started to popup(i.e. “Tiny 2040”). Curious of the debug options that will be available (Seggear J-link?, Picoprobe?). Thanks.