XPost: sci.electronics.design   
   From: wwm@wwmartin.net   
      
   Hi All,   
   Anyone doing stuff with both cores on the Pico? I just grabbed the Pico   
   extension for Visual Code to poke it & see what it does, had an   
   interesting first adventure. It does not seem to know anything about   
   setting up a muticore project, so I had it generate a simple project   
   that it did understand, just "example" level stuff, replaced the   
   generated .c file with my own little test case...#include   
   "pico/multicore.h" is not findable. So, looking at the generated   
   compiler commands file, I added in a -I/home/.../include explicitly to   
   see what happens. No change, still not found. hmm. Is there some magic   
   caching going on here? Next, I added a -D for the multicore library,   
   still no change. Noticed that I had forgotten to add the pico_multicore   
   lib to the CMakeLists.txt file and behold it builds now, no missing .h   
   files. So my "solution" isn't really good for anything more than a   
   casual kicking the tires thing, and I'd really appreciate it if sommeone   
   could guide me a little on how to do this "right". Do I just have to   
   wait for the VSCode extension to get smarter, or is there a better way   
   to get those .h & .lib paths known to the compiler?   
   Thanks,   
   Bill   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)