I just installed the Pico VS Code extension and I am trying it out on a Raspberry Pi 4B with the latest Raspberry Pi OS
I was able to create, build, and run the blink example as a Pico project.
I have an existing Standalone project that uses the SDK and builds fine from the command line using the Unix Make Generator. The project has multiple Target binaries in multiple directories and with the current generator it puts make files in each directory and one may go into a particular directory and make only that particular firmware. I noticed if I use ninja as the generator from the command line it puts all of the make files in the build directory and you have to reference that path to build an individual program.
The behaviour of my project with the extension after I imported it is the building will build all of the executables and if you hit run it wants to run a phantom.elf that doesn't exist but the extension tries to use the project name for the elf.
Here's my question, does each Pico project equal one piece of firmware or is there a way to have multiple programs under one project? Can I modify the build and the run commands in the extension to only build and run individual files within a main project or are we stuck making an entire project for each firmware file, in other words?
Can I create custom Pico extension .json files for a project I have on GitHub so when it is cloned it is ready to do these things that I want it to do?
Or do I need to now go and reconfigure all my cmake files?
I was able to create, build, and run the blink example as a Pico project.
I have an existing Standalone project that uses the SDK and builds fine from the command line using the Unix Make Generator. The project has multiple Target binaries in multiple directories and with the current generator it puts make files in each directory and one may go into a particular directory and make only that particular firmware. I noticed if I use ninja as the generator from the command line it puts all of the make files in the build directory and you have to reference that path to build an individual program.
The behaviour of my project with the extension after I imported it is the building will build all of the executables and if you hit run it wants to run a phantom.elf that doesn't exist but the extension tries to use the project name for the elf.
Here's my question, does each Pico project equal one piece of firmware or is there a way to have multiple programs under one project? Can I modify the build and the run commands in the extension to only build and run individual files within a main project or are we stuck making an entire project for each firmware file, in other words?
Can I create custom Pico extension .json files for a project I have on GitHub so when it is cloned it is ready to do these things that I want it to do?
Or do I need to now go and reconfigure all my cmake files?
Statistics: Posted by breaker — Fri Jan 03, 2025 6:50 pm