I adjusted all 5 settings in settings.json as recommended:See the readme, you’ll need to use the CMake Tools Extension Integration to work with projects with multiple executables (https://github.com/raspberrypi/pico-vsc ... ntegration)
“For more complex projects, such as those with multiple executables or when the project name is defined as a variable, this extension can integrate with the CMake Tools extension to enhance CMake parsing.”
I selected the Pico kit, re-loaded, also I changed the board from pico2 to pico for fun.CMake Tools Extension Integration
For more complex projects, such as those with multiple executables or when the project name is defined as a variable, this extension can integrate with the CMake Tools extension to enhance CMake parsing. You can enable CMake Tools integration during project generation under the Advanced Options. Additionally, to manually enable it, adjust the following settings in your settings.json:
raspberry-pi-pico.cmakeAutoConfigure: Set from true to false.
raspberry-pi-pico.useCmakeTools: Set from false to true.
For optimal functionality, consider enabling:
cmake.configureOnEdit: true
cmake.automaticReconfigure: true
cmake.configureOnOpen: true
When prompted, select the Pico kit in CMake Tools, and set your build and launch targets accordingly. Use CMake Tools for compilation, but continue using this extension for debugging, as CMake Tools debugging is not compatible with Pico.
Upon re-launch of VS Code it does the generating of make files, and near the end there were these errors before the build step, but it built. I don't want it to auto-build on launch though. These errors seem not a problem:
Code:
[proc] The command: arm-none-eabi-gcc -v failed with error: Error: spawn arm-none-eabi-gcc ENOENT[proc] The command: arm-none-eabi-g++ -v failed with error: Error: spawn arm-none-eabi-g++ ENOENTStatistics: Posted by breaker — Thu Jan 09, 2025 8:48 pm