I think we can forget about that. The problem seems more fundamental than me doing something wrong.has anyone got a project which builds using the VS Code Extension they could Zip-up which I could use ?
On a recent run the code got to a "Do you want to import a project?" but the pop-up disappeared before I had a chance to respond to that and I was left with the progress bar 'pong paddle' always scrolling, no way to resurrect the pop-up that I could see.
I tried again and managed to click "Yes" and "import" but that didn't seem to do anything, produced more "Variable "path" should be a string; undefined" errors, briefly popped-up a couple of somethings which disappeared before they could be read.
Earlier times though it didn't get that far. I resorted to just forcing the 'isPicoProject' flag true and that's enabled the "Compile" and other "Project" based options, but it seems more needs to be done.
"Switch SDK: Current N/A" appears to mean it can't find the SDK it installed so it went through the rigmarole of downloading and installing that again, overwriting what already existed. And after that it failed with "path" not being a string. Along the way it deleted the examples previously downloaded.
I am sure it could be made to work on 32-bit if I knew what I was doing and was familiar with extensions, but it seems to be more effort than I think worth expending at present especially as VS Code is mostly usable for compiling Pico projects as it ever was without it, just using 'CMake Tools'.
I'm sure the Pico Extension is great for some when it works but all I was really after was an trivial means of setting 'CMake Tools' to build a single source project for various boards, as Run From Flash, Copy to RAM, Run from RAM variants, something as easy as changing build types is, debug, release, etc.
But, from what I can tell, Pico Extension isn't designed to create multiple builds into multiple build directories from a single project source. It doesn't even seem to support boards other than Raspberry Pi offerings so anything else will probably still requires the convoluted process of tweaking 'CMake Tools' settings or editing 'CMakeLists.txt'.
So, not for me, I think. I might take a look again at creating what would be an "RP2 focused CMake Tools" extension, see if anything I've learned helps with that.
Statistics: Posted by hippy — Tue Nov 19, 2024 9:42 am
